Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Moving Open stories when closing a sprint.

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.

1 comment

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 08, 2022

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"

Like Greg Fichtner likes this

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-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 08, 2022

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.

Like Greg Fichtner likes this

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. 

Comment

Log in or Sign up to comment