- On a brand new JIRA instace (tested on 6.0.5); install Greenhopper (6.2.5)
- Better handling of sample data generated
- Custom Field names.
- Issue Type names.
- Issue Type Scheme.
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.