Done stories

[Pallavi_Satpute]

I wish to remove the User Stories completed in previous sprint from the Sprint Backlog of current sprint. i.e. stories which were in ' Done' status in current sprint should not appear in the sprint backlog of next sprint after the current Sprint is closed. How to do this?

[Marc -Devoteam- · Accepted solution]

Hi @Pallavi_Satpute 

Welcome to the community

For a work item to be considered 'burned' (done) in a sprint. 

The most right column of a sprint board should contain the last state of a workflow to consider the issue to be finished in the sprint.

[garrett_lessard]

Hi there,

Jira will not automatically filter out Done issues from a sprint closure if they are still tied to the upcoming sprint. Normally, when you close a sprint, Jira leaves completed issues right where they are and only asks what to do with the unfinished ones.

If your Done stories are still rolling over, it is usually caused by a configuration mistake. Here is how to fix it based on what is likely happening.

1. Check your board column mapping

Jira tracks completion by status category, not column names. Go to your Board settings and click Columns. Make sure every status in your Done column is set to the green Done category. If any of them are still marked as In Progress, Jira will think the work is incomplete and try to carry it forward. This is the most common reason this happens.

1. Check for automation rules

Jira does not move completed issues to new sprints on its own, but a rogue automation rule might be doing it. Go to Project settings then Automation and check your active rules. Look for anything that automatically updates the Sprint field when a sprint ends or a status changes, and make sure it excludes Done issues.

1. Verify the issue's sprint field

Sometimes issues accidentally get assigned to multiple sprints at once. Look at one of the problem stories and check its Sprint field. If it lists both the old sprint and the new sprint, it will keep showing up on your current backlog. You can fix this in bulk from the backlog view by selecting the issues, clicking the three dots, and removing them from the future sprint.

1. Check your board filter

If your board filter is too broad, it might be pulling in past sprints alongside current ones, making it look like old issues are rolling over when they are actually just still matching the filter. Check your board's JQL query to ensure it is focused only on the active project and current work.

What to do next:

Let me know if you are using Jira Cloud or Data Center, and whether these Done issues are actually getting the new sprint name stamped on them or if they are just stuck on your board view. That will help pinpoint the exact fix.

Cheers,
Garrett Lessard Appfire Expert Services

[Marc -Devoteam-]

Hi @garrett_lessard 

it's not according to community guidelines to necro-post on old post and certainly not on already solved posts.

What is your intention here, as the post is already marked as resolved?