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
Before integrating Jira with Jira Align, there are some best practices that should be considered. Some are a little more rigid than others; while others can lend themselves to some workarounds. Let's explore further to understand what these are, why these are important and the potential impacts.
Fix versions in Jira are created by project and could potentially create duplicate release vehicles in Jira Align that represent the same release.
Why: When using 1 project to 1 board structure, each project has its own fix version that could be duplicated over projects. All of these fix versions will sync over to Jira Align as individual release vehicles.
Workaround: Grouping release vehicles in Jira Align is an option but will not solve this as all of the fix versions will still be created as individual release vehicles in Jira Align.
If wanting to assign releases to features, release vehicles would need to be created in Jira Align and fix versions would need to be created in Jira. In turn, these should not be synced with each other and would need to be maintained manually.
Why: The recommendation is to not sync release vehicles in Jira Align and fix versions in Jira. Due to this, if there is a need/desire to track work by release, it would need to be maintained manually.
If the Fixed Version sync between Jira and Jira Align is enabled in the Jira connector settings: