Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Why do "Done" issues still showing in next Sprint? Edited

As title, how do I change that?

1 answer

2 votes

My guess would be because the issues were not flagged as "done" when you ended the previous sprint.

"Done" on a scrum board is the last column on the board, not just a done status or a filled resolution.

I have to move every "Done(status)" issue to "Done" column on the board view? Is there any faster way to do this in once?

You should be doing it during the sprint as your developers complete the stories.

But if you need to do a tidying up exercise in bulk, yes, you can search for the issues and then use bulk-edit to transition them through the workflow into a status that is in the last column.

I've just test it, when assignee change the issue status from X to "Done", in Board view, the issue will automatically move to "Done" column. then why do these "Done" issues still showing in current Sprint? @@a 

Because a sprint shows what is currently in it, irrespective of status.  The whole point of the sprint is to contain a set of issues that you've committed to doing.  And the board is there to show progression, including all the stuff you've marked done.  It doesn't drop "done" issues, the whole point is that you can see that they're there.

When you close the sprint, items done in that sprint will be seen as closed issues - they won't appear in the backlog, or in the next sprint because, well, they're done and the new sprint should be committing to doing the next selection of issues that need doing.  If an issue is not done when you finish a sprint, it will go into the next sprint, because it needs more work doing.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

297 views 9 7
Read article

Community Events

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

Events near you