-
Suggestion
-
Resolution: Tracked Elsewhere
-
None
NOTE: This suggestion is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding suggestion.
When upgrading GreenHopper, can you please verify if they are using the correct Issue Types? We do a lot of verification on the Custom Fields now and lock them down if they're the defaults, however there's no verification of Issue Types.
GreenHopper can somehow get into a state where the Issue Types are not correct in the database and this will cause all sorts of problems, such as the linked issue.
Thanks!
Workaround
This can be fixed using How to Fix the Duplicate GreenHopper Custom Fields After Upgrading, specifically steps 4 - 9.
- is related to
-
JSWSERVER-8671 When upgrading, please verify the Issue Types are correct
- Closed
- relates to
-
JSWCLOUD-6927 If another Issue type exists with default Epic ID, Greenhopper treats it as the new Epic.
- Closed