Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Getting error: multiple jira align sprints are mapped to a signle jira align team sprint

Getting error multiple jira align sprints are mapped to a signle jira align team sprint

though as per the screenshot you can see only one sprint is mapped to one jira align sprint. multiple jira align sprints are mapped to a signle jira align team sprint.png

2 answers

I haven't seen that error in quite a while.  The updates from Atlassian typically keeps that from happening now. 

The only thought I have is to check the anchor dates for the sprints that have been suggested and are currently mapped to the Jira sprints.  There have been times where I've seen the anchor dates are not set up properly and are mismatched on the Align sprints.  Take a look at this example screenshot.  My Align sprint has one set of dates, but the sync(anchor) date

is a different time.

Also, have you tried syncing the board again?

Screenshot 2023-10-05 at 10.40.21 AM.png

We are having the same issue, it seems to coincide with migrating Jira Server to Jira Cloud.  Also, once the sprint mapping error is resolved (and it is rarely actually bc there's more than 1 sprint trying to map), the error flags do not clear and it is maddening!


My process for resolving is to make sure there not an extra scrum board pulling in the sprints of the JA connected board. Then I check to make sure all of the dates on the sprints on the JA connected board are right.  Then I go in JA and delete the unlocked sprints, then in Jira Settings go to the Jira Intergration tab and sync the project and the board. 95% of the time this fixes the actual error.  Doesn't clear the flag, but fixes the actual problem.

That's interesting.  I've seen some strange behavior after migrations from server to cloud, or merging multiple Jira instances to one.  

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events