Rank field migration explained
Brief
This will explain the Rank field migration from GreenHopper 5.7.4 to GreenHopper 5.8.3.
Previously, 5.7.4 shipped with "old" rank field as well as Global Rank field implementations (single field support only, in labs mode). 5.8 upgrades all old fields to new Global Rank Fields (see GreenHopper 5.8 Upgrade Notes).
Explanation
GH 5.7.x (<= GH upgrade task 11):
5.7.x shipped with the Global Rank Field in labs mode. Unfortunately the field wasn't completely "stealth". Each newly created issue was added to the global rank index as well (regardless whether Labs was enabled or not). Together with the index being less "secure", GH could end up blocking the rest of JIRA whether or not Labs was used at all!
GH: 5.8.x (upgrade task 12, 13, 14 (5.8.3 only)):
Upgrade task 12 moves the Global Rank field data from one AO table to another, which was a precondition to support multiple rank fields.
This upgrade task (UT 12) migrates data from AO_60DB71_RANK_ISSUE_LINK (old, single rank index table) into AO_60DB71_ISSUERANKING (new, multi-field global rank table). If there is already data in AO_60DB71_ISSUERANKING, it will fail so once it is determined that the data in there is not needed, clearing out that table will do the trick |
Upgrade Task 13 migrates all old rank fields to new global rank fields. For each old rank field a global rank field is created (same name!), then the data is migrated to the global rank field and in a final step the old field type changed to a plain "Custom Number Field".
Upgrade Task 14 adds a flat to ensure GreenHopper properly blocks until all upgrades are complete.
com.atlassian.greenhopper.upgrade.UpgradeException: Attempting to migrate data from Labs ranking table to new ranking table, but new table already contains data
If you come across the above error, you will need to remove the contents of the AO_ 60DB71_ISSUERANKING table (where 60DB71 is subject to change, so look for AO_anything_ISSUERANKING in the database if you can't find the first option). Once removed, restart JIRA and it should perform the upgrade fine.