JIRA Agile Upgrade Duplicate Custom Fields Error Message
The purpose of this knowledge article is to inform the user that the error has been flagged and no more duplicate fields should be created.
Symptoms
Upgrading GreenHopper after 6.1.4 has been known to create duplicate custom fields as described in the two knowledge articles:
- How to Fix the Duplicate GreenHopper Custom Fields After Upgrading
- Deleting Duplicated Locked Sprint Customfield for GreenHopper
The error message should similar to the following:
Custom field 'Story Points' with ID '%s' exists in DB, but was not returned by the issue field manager.
Custom field 'Sprint' with ID '%d' exists in DB, but was not returned by the custom field service.
Custom field 'Rank' with ID '%d' exists in DB, but was not returned by the custom field service.
Custom field '%s' with ID '%d' exists in DB, but was not returned by the custom field service. (first %S replaced by Epic Name, Epic Label, Epic Link, Epic Color)
Cause
The original cause of the issue is still unknown, however the duplicate creation of these fields should have stopped and should no longer be an issue.
Resolution
- Please restart GreenHopper plugin, if this fails, then restart JIRA.
- If this fails, please log a support.atlassian.com ticket and attach a JIRA Support Zip.
Last modified on Nov 1, 2018
Powered by Confluence and Scroll Viewport.