Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,328,538
Community Members
 
Community Events
168
Community Groups

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

Edited

As title, how do I change that?

1 answer

1 accepted

3 votes
Answer accepted

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.

Like Petter Gonçalves likes this

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.

For me it is marked done. I close the spring the done items still move to the next sprint.

I realized i needed to make it the last column in the Kanban. 

Suggest an answer

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

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

2,785 views 7 23
Read article

Atlassian Community Events