Warning "Jira Align team sprints are not mapped in calendar order" after syncing Jira Board
Summary
This article outlines the possible solution(s) to resolve the warning message “Jira Align team sprints are not mapped in calendar order. Verify that your mappings are correct.” seen in the Jira Sprints tab under the Jira Connector Jira Management page.
Environment
Jira Align
Diagnosis
Under Jira Align's Administration > Jira Management > Jira Sprints tab, the following message is displayed when you hover over the warning icon.
Cause
By default, the connector maps the first integrated sprint based on the end date and all following sprints based on the order of the sprints on the Jira board. If a new sprint has been created later with an older date than the previous one, or the ordering of existing sprints has changed, then the mapping is not considered to be in calendar order.
In the example above, the order of Sprint 2 is before the one of Sprint 1, and its end date is after the dates of Sprint 1.
Solution
For sprints that are still open, it's possible to swap them to the correct order in the UI. To resolve this warning message for closed sprints Jira API can be used:
Check the order and the dates of the Sprints in the Board using the Jira API
https://<jira-host-server>>/rest/agile/1.0/board/<boardId>/sprint
(eg: <https://alignsupport.atlassian.net/rest/agile/1.0/board/402/sprint)
Swap the position of two Sprints to change the order of the sprint on the board using the Jira API
https://<jira-host-server>>/rest/agile/1.0/sprint/<sprintId1>/swap
with the POST request body:{ "sprintToSwapWith": <sprintId2> }
- Now, check again the order and the dates of the Sprints in the Board using the Jira API
- Resync the board in Jira Align to see the new order:
The original warning “Jira Align team sprints are not mapped in calendar order. Verify that your mappings are correct.” is now gone and only remains the unrelated ones.