Moving Open stories when closing a sprint.

[Greg Fichtner]

According to the documentation:

Completing the active sprint

1. Go to the Active sprints of your Scrum board.

2. If necessary, select the sprint you want to complete from the sprint drop-down.
   Note that if you have multiple sprints in the Active sprints of your board, the 'Complete Sprint' button will not appear until you select one of the sprints.

3. Click Complete Sprint. All completed issues will move out of Active sprints.

4. If the sprint has incomplete issues, select from one of the following:

   • Backlog, to move the issues to the backlog

   • Any future sprint, to move the issues to any future sprint that's already created

   • New sprint, to create a new sprint and then move the issues to the new sprint
     
     ============
     The book says "move" to the backlog or "move" to a future sprint, BUT  - the tool is keeping the completed sprint in the story and then adding the new (open) sprint to the story.  Is there any way to fix this?  It would be a nice feature otherwise.

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

"Move" is a bit of a misnomer in this case.  What it means is "put the issue into another sprint, but retain the data about the old sprint(s) the issue has been in".

If it did not do that, none of the sprint reporting would work.

There is no way to "fix" this, you need the data that issues were in sprints.  Atlassian are unlikely to change this, although some of us have asked for them to split the data into "previous sprints" and "current sprint" - the request was closed with "won't fix"

[Greg Fichtner]

Thanks for your reply Nic.  Please let me know which (or what part of) sprint reporting requires this so I can pass on to my organization. 

In order to avoid this, a user has to manually move any stories (before closing the sprint) that didn't finish by sprint end.  This seems like this would "break" the sprint reporting as well.

I am really interested in using the automation provided, but probably need really good justification for it.

Thanks!!!

[Nic Brough -Adaptavist-]

All of it!  Almost all the reports are based on "sprint = X" in one way or another, so if you destroy that information, the reports stop working.

You should not be moving stories by hand, you should let the "sprint closing, move open stories to the next one (or backlog)" function do it for you.  If you do it manually, you're recording inaccurate scope change.

[Bas de Kort]

Hi, does anyone know to put the unfinished stories that are moved from sprint x to x + 1 *on top* in the next sprint. The prepared stories in the next sprint are complete mixed when the current (unfinished) stories from the current sprint are added to it.