I wanted to provide a high-level distinction of the Issue Type migration or integration process:
Migration- If you use Issue Type in your instance that are defined hierarchically higher-level artifacts than a Jira Epic, you should have a plan to match them to Jira Align (Initiatives and Thems as examples). Jira Align provides a template that can be prepared for uploading.
Integrations- Jira Epics, Stories, and relevant Issue Types can be mapped in the Jira Setting configuration. Additionally, issue types used as additional Story Types can be mapped in the Jira Align configuration. Issues that are mapped in this process retail their IDs.
@Hopkinson, Peter can you provide some more details as to what you are expecting to accomplish? We don't normally migrate teams from Jira to Jira Align and instead integrate the teams work (execution) with Jira Align (strategy). We have a bunch of articles on the integration and how you can see stories in Jira with it's link to Jira Align and vice versa.
Here is the community pages on details around the Jira and Jira Align integration. https://community.atlassian.com/t5/Jira-Align-articles/Jira-Align-and-Jira-Integration-Best-Practices-and-FAQ-Table-of/ba-p/1253497
The roadmap challenge for large scale agile enterprises Regardless of the agile framework you use, the agile enterprise has a massive scale with the challenge to connect hundreds of teams and thous...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events