You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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