Board sync is causing the team sprints to get updated in turn updating the Program Increments in Jira Align
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
Sprint mapping is set up correctly, however, when the Board sync is initiated the team Sprints get updated. This in turn triggers an update to the Program Increment.
Diagnosis
Analyzing the team audit log in Jira Align, we can see that the Sprint update has caused the Program increment to update appearing as created by External system
Checking further, we could also see that the Program was part of two parallel PIs - both with the same start/end dates and the same anchor start/end dates.
Cause
Sprint misalignment can be causedby overlapping anchor dates in the PIs. The basic rule is that, a team or a program should never be in two places at once ie, it should not be in two overlapping PIs at the same time.
Solution
Consider there is a Program mapped to two different PIs with same start/end dates and with same anchor dates. In order to create Sprints in JA, a Story is created in Jira with the same sprint date as the JA anchor start/end date. Once we initiate a board sync, notice that the team Sprint was mapped to the latest(last) created anchor date in Jira Align; also changing/updating the team PI.
This issue is caused by overlapping anchor dates in the PIs. A team or a program should never be in two overlapping PIs at the same time. This issue can be resolved by changing the anchor dates of one of the PIs ensuring that it does not share the same start/end date with any other PI.
This is clearly explained in the video in this help article. Please watch the video from timestamp 2:24m.
Was this helpful?