COS:

• manually triggered for a whole project
• show the number of issues to be updated before you hit go
• make it clear that this only migrates data that exists right now - it does not synchronise the relationships over time. also make it clear that it can be re-run at a later time if necessary.
• put in the global config in a new tab – Classic Epic Migration
• explain what is about to happen when they proceed:
  • find issues with an issue key in the 'Epic / Theme' field then convert this to an Epic link. If a story is already linked with Epic Link field, ignore it.
  • server-side logging
• notify the Admin on confirmation page they should remove the Epic / Theme field (if it is no longer being used)
• modify description of Epic/Theme custom field so that it references Classic Boards

Development Notes

Q: Need to try with data from epics still in labs
A: Not Answered

Q: What happens when editing the old epic links?
A: The old epic links can be updated but are not synced to the new style of epic link. Another migration is needed to port over the updated classic epic link (this will only work if the target issue has not yet been linked to a new style epic link)

Q: If you update classic epic links, will new ones be created as well from now on?
A: No, there is no synchronization between old and new epic links

Q: What if there is old epic label data from when epics was still in labs (aka field is named something else)?
A: Upgrade tasks will have migrated it. The migration uses the configuration of classic mode to find the classic epic link custom field

Q: Are there any differences with JIRA/AO versions we need to be wary of?
A: Nope