In Jira Align, ADO Stories (PBIs) lose their Parent Feature when assigned to a new Sprint (Iteration Path)
Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When changing ADO stories (PBIs) to a new sprint, check the timebox (Release/PI) of the parent Feature. If the new sprint is not in the same timebox, synchronization will not occur.
Environment
Jira Align
Diagnosis
Moving ADO stories (PBIs) to a new sprint has their JA counterpart lose the parent Feature
Cause
In ADO: The child story was moved from Sprint 1.5 into Sprint 2.1.
In JA: The parent feature was still in PI 1.
Changing the Story's Sprint in ADO will not put the Story into a new Feature in JA so the change of sprint causes a misaligned Story, which Jira Align sees as being in the wrong PI, so won't set the Sprint.
Solution
To avoid this issue in with moving stories between sprints in different PIs in ADO, the correct order of events is
In ADO Put the Story in a Feature that is in PI-2 first.
Then change the ADO Iteration Path.
These steps should then result in the story replicating correctly over to Jira Align.
Was this helpful?