Hi Community,
I've recently integrated one portfolio with multiple programs (Jira to Jira Align). The PI and anchor sprint start and end dates are aligned. And the various sprints in Jira are aligned with the PI's start and end dates. The sprint buffer days = plus/minus 2 days. Bi-directional syncing with Features; Jira to Jira Align syncing with Stories.
However, when we synced sprints, the 1st sprints items did not load into the sprint. But the items for the rest of the PIs sprints populated in the various sprints just fine. I do see all the sprints in the Fit View in Jira settings and I do see the stories that should be in sprint one in the story backlog.
We did see the below message in the Spring Logs and reviewed the dates but there seems to be nothing to do. The dates area all aligned. → Reason : Sprint could not be mapped. Check release sync dates to see if Jira Sprint can be mapped. The Jira Sprint has a date range of: 2023-07-19T13:57:00.000Z - 2023-08-02T1
Our JA Ent. Sol. Strategist is excellent! But we haven't been able to figure out what happened. We tried resyncing but it didn't work.
I was wondering if the solution would be to just add the sprint in Jira Align and assign the items to it. but, I don't know the impact of doing it that way.
Your help is appreciated.
Notes:
yep. I'll do that next. just thought i'd ask here.
thank you.
yes, it is a good try :-) I was curious and looked into the log of our demo instance and found the same warning. I will check here what caused it and let you know.
So I can confirm the answer of Ahmet below: I was able to resolve the messages by checking:
* are JA anchor sprint dates in line with Jira board sprints
* are all JA team sprints generated from the anchor sprints
* are all JA team sprint dates matching the Jira sprints
Having added one missing sprint and correcting one date fixed the issue in our instance.
Hi Apryl,
I assume you have configured the dates of 1st sprint accordingly. But anyway, the mapping is not working and stories are not populated.
I got a similar problem and after recreation and mapping the sprints it was working somehow.
Otherwise, just reach out to Atlassian Support there are some nice guys that would be happy to help you dig into it.
Use the link below:
https://support.atlassian.com/contact/
Warm regards,
Ahmet Kilic
Enterprise Agility Consultant at catworkx
looks likes whole catworkx is chasing the issue! :-)
Cool! As Atlassian Enthusiasts, we're glad to help the ecosystem. :)
@Apryl Harris A couple of things to check...
There were a lot of steps in this so if any of this doesn't make sense, I would recommend you open a ticket with Support and they can assist you as well.