While struggling with issues not showing up in Advanced Roadmaps like several other users, I have finally noticed that sprints assigned to issues seem to not be handled exactly the same way between JIRA and Advanced Roadmaps.
The difference seem related to the way Resolution status is handled and this is also potentially linked to the way workflow and resolution status is configured.
Here is a concrete use case.
- Story workflow is defined in the way that Resolution Status is set while transitioning to a given 'Solved' state (meaning that the story has been implemented) while there is still a transition after to a given 'Closed' state (meaning that the story has been effectively released)
- 1 sprint Sprint_A from Apr-19 to May-7
- 1 sprint Sprint_B from May-10 to May-28
- 1 story Story_X has been set to 'Solved' state during Sprint_A but set to 'Closed' state during Sprint_B
According to this picture, then
- JIRA assigns Story_X to Sprint_A AND Sprint_B
- Advanced Roadmaps assigns Story_X to Sprint_A ONLY
As a consequence, when showing issues assigned to Sprint_B in Advanced Roadmaps, the issue Story_X does not show up while it be effectively visible in the JIRA board.
Following this observation, my main question is to wonder why sprint values are just not directly reused from JIRA to Advanced Roadmaps but that is probably easier said than done.
Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events