Why would future sprints show up out of order in the backlog board view?

Question

We are using an agile board that contains work for multiple teams.

The 2nd team is naming their sprints differently, such as "Sprint ATeam 10/1-10/15"

I had created sequential sprints for the rest of the year:

- Sprint 1 10/1-10/15

- Sprint 2 10/16-10/30

- Sprint 3 10/31-11/14

- Sprint 4 11/15-11/30

They started showing up out of order this week, for example:

- Sprint 1 10/1-10/15

- Sprint 3 10/31-11/14

- Sprint 4 11/15-11/30

- Sprint 2 10/16-10/30

Any thoughts on what causes future sprints to be rearranged?

* Could it be related to toggling between "Sprint ATeam 10/1-10/15" and "Sprint 1 10/1-10/15" views?
* Could it be related to experimenting with the left "Epic" panel in the board view

We can fix it manually by moving the sprints but concerned this will keep happening. Thanks for your help!

Bea Tea · Answer

Thanks for the reply @Petter Gonçalves ! I was actually in a different view which is the backlog view of the board url like:

jira.com/secure/RapidBoard.jspa?rapidView=12345&projectKey=ABCDE&view=planning&issueLimit=100

Do you mean that if we ever used/setup the advanced roadmap plan then this could be the issue?

Petter Gonçalves · Answer

Hello @Bea Tea

Thank you for reaching out.

Indeed, The scheduler of Advanced Roadmaps is incapable of accurately scheduling future Sprints when running parallel with multiple Teams at once. We have a feature request to properly improve this functionality in the future:

Parallel Sprints scheduling with multiple teams

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

A workaround option would be to:

* Create a filter for each team that extracts only the tickets for this team
* Optionally you can create a board in the project for each of these filters which can be convenient for each team to see only their tickets
* Instead of using the project board as the issue source for the plan, create one issue source for each team board
* In the plan, edit each team to associate it with the corresponding issue source

Doing the steps above, the scheduler will be able to plan the work of the different teams in parallel.

Let us know if you have any questions.