-
Bug
-
Resolution: Tracked Elsewhere
-
High (View bug fix roadmap)
-
None
-
6.2.2.2, 6.2.3, 6.2.4, 6.2.4.1, 6.2.5
-
None
-
6.02
-
Steps to reproduce
- On a brand new JIRA instace (tested on 6.0.5); install Greenhopper (6.2.5)
Expected Results
- Better handling of sample data generated
This is affecting the following names and descriptions
- Custom Field names.
- Issue Type names.
- Issue Type Scheme.
Workaround
If this is a fresh installation and contain no valuable data, we encourage to re-do the whole installation process with an empty database, follow the steps below:
- Uninstalled JIRA and clear the data
- Install JIRA and create a backup directly
- Install GreenHopper and Reindex
- Noticed that the problem still persist
- Perform a system restore with the backup data created earlier
- Double check that the problem is resolved after the restore
Thank you Matthew for pointing this out
If the instance is being used for production:
- Unlock the GreenHopper Custom Fields as per our How to unlock a Locked field KB. This will enable them to be editable.
Please lock them back after making the changes so as to prevent any accidental changes to the configuration, which can break GreenHopper. - If there are duplicated Issue Type names (e.g.: "Story" and "gh.issue.story"):
- Bulk Edit the old Issue Types to the new ones as per our Modifying Multiple ('Bulk') Issues docs. For example, if there is a "Story" Issue Type, move those issues to "gh.issue.story".
- Rename "Story" to "Story (unused)" and remove it from all the Issue Type schemes.
- Repeat these steps for any other duplicated Issue Types.
- Rename the Issue Types, Issue Type Scheme, Workflow Name, Workflow Scheme and Custom Fields through the browser to human-readable names (e.g.: rename the Issue Type "gh.issue.story" to "Story").
- Reindex JIRA, so as to update the indexes with the new names.
- is caused by
-
-
- Closed
-
-
JRADEV-23317 Failed to load
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-9193] Custom Fields, Issue Types and Schemes appear incorrectly on a new install of Greenhopper
David notes that this is caused by another bug JRA-33966. Unless I'm mistaken, that bug is marked as closed and is incorporated in Jira versions 6.0.6 and 6.1-OD-05.
How is this marked as resolved? The workaround for production use is untenable. A new plugin version should be released that will detect and programmatically resolve the issue. Will updating to JIRA 6.0.6 where JRA-33966 is fixed also fix this issue or will the workaround still be necessary?
Aaron Daubman
added a comment - - edited How is this marked as resolved? The workaround for production use is untenable. A new plugin version should be released that will detect and programmatically resolve the issue. Will updating to JIRA 6.0.6 where JRA-33966 is fixed also fix this issue or will the workaround still be necessary? This is caused by a bug in JIRA as tracked under JRA-33966.
Edit: Massive thank you to vkharisma for putting the original workaround in 
Patrick Baker
added a comment - I was able to get a fresh installation of JIRA 6.0.5 and Greenhopper 6.2.5 to work. The key was restarting after each major operation.
- after installing JIRA, restart
- upgrade UPM/plugins, restart
- install greenhopper, reindex, restart
Patrick Baker
added a comment - I was able to get a fresh installation of JIRA 6.0.5 and Greenhopper 6.2.5 to work. The key was restarting after each major operation.
after installing JIRA, restart
upgrade UPM/plugins, restart
install greenhopper, reindex, restart
A few more comments:
- Uninstalling and re-installing fresh as suggested above did not solve the issue
- I was able to get some success with the workaround noted above, but would much prefer the system had doen the configuration for "peace of mind"
- Ultimately, the best solution came from reading through the comments in the related issue noted above
GHS-9238which suggested to restore a backup to solve the problem. I did and it works beautifully. Mine was a fresh install, but i think the key is take a backup of Jira BEFORE you install Greenhopper. Here are the steps I took: - Installed Jira
- Took a Jira backup from the Jira System admin page
- Installed Greenhopper
- Restored the Jira backup (pre-greenhopper) from the Jira System admin page
- Go check out the issue types in the Jira Issues admin page and they are fixed
Hope this helps others in the same situation.
Justin - Go to page 357 of the GH 6.2 docs and you will find the custom fields and issue types. https://confluence.atlassian.com/display/GH/GreenHopper+Documentation
I was referred to this issue after logging an issue and I agree that the workaround description is far too vague.
I have these symptoms after an upgrade from Jira 5.1.3 to 6.0.4
We already had Greenhopper installed and simply upgraded the plug-in after the Jira upgrade. There was no "sample data" involved, although plenty of production data existed in the database because the software is in active use on our project.
Lastly, I'm not sure what's meant by "Rename ... name/description from the UI". Should we copy the text from the Type column (as in your final screenshot ) and use that or is there somewhere else we should get these correct field names?
daubman, this is marked as resolved as it's tracked in
JRA-33966as it is caused by a bug within JIRA. The symptom presents in GreenHopper, hence why there are bugs raised here. As for the actual fix, I tested by upgrading my affected instance to 6.0.6 and it did not appear to update the affected fields, so I reopenedJRA-33966as in this comment.For future updates to the bug, please comment and watch
JRA-33966- thanks, and kudos thierry.lach for commenting on the issue.