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:
Rae GibbsAtlassian Team
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