Help! Closed Sprint Under Wrong Board

[Corey K]

While managing several different project teams in Jira a sprint was closed using the wrong board ..meaning someone closed the sprint using ABC Board but should have used XYZ Board which would have naturally seen all roll over issues falling under the correct new sprint.

In other words the correct sprint which issues should be falling under should have been"XYZ Sprint 2" but that is now still considered a "Future Sprint" while the roll over items are currently rolled under "ABC Sprint 2". 

What is the best way to fix this situation while not completely throwing my engineering teams off their game. 

[Mikael Sandberg]

You can always reopen a closed sprint if you go to Reports > More reports and select the Sprint Report. From here select the sprint in question and then click on the three dot menu on the right hand side and select Reopen sprint. You can then close it from the correct board so the open work items are moved to the next correct sprint.

This happen because sprints are not board specific, so I always recommend assigning work items from the board in order to avoid picking a sprint that "belongs" to a different board.

[Gor Greyan]

Hi @Corey K

Welcome to the Atlassian Community!

This can be corrected without undoing the completed sprint.

When a sprint is shared across multiple boards, the board from which you complete the sprint does matter for the rollover of incomplete work items. Atlassian documents that only incomplete work items belonging to the board used to complete the sprint are carried over to the selected future sprint; incomplete items belonging to other boards are moved to the backlog instead.

In your situation, if the affected work items should now belong to XYZ Sprint 2, I would leave the completed sprint as-is and move the incorrectly rolled-over items to the correct future sprint from the backlog.

Before doing that, I would also check the filters for ABC Board and XYZ Board. If their filters overlap, the same work items/sprints can be visible across the boards, which can make it easy to complete a shared sprint from an unintended board.

Also check this doc.

https://support.atlassian.com/jira/kb/sprints-appearing-on-multiple-boards-in-jira-data-center-server-or-cloud