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

How to remove closed issues from the current sprint?

Hi there,

I have a growing list of issues that keep on being included every time I create a new sprint. Those issues are done (Resolution) and closed (Status).

How can I remove them from the current sprint so that they stop being carried over every time?

Thank you

2 answers

1 accepted

0 votes
Answer accepted

Is the status "closed" in the right-most column on the board?

It's not. Should it? The sprint board is only one part of the whole workflow, issues moved to the last column of the sprint board are picked up by another kanban board.

Yes, the last column on the board is the "definition of done" for Jira.  If a card is not in the right hand column, it is not "done"

ok thank you, that explains it. It seems rather limiting though, because cases can be closed for other reasons on other kanban boards. I'll try and find a workaround.

 

Thanks!

I have the same issue @Christophe L. 

Each time we close a sprint (~monthly) there are additional issues that are rolled over to the new sprint

Within each sprint, we do a number of releases and 'releasing' the tickets in JIRA sets the status of the tickets in that release (aka fix version) to 'Closed'

Only 1 sprint is active at any time, and the 'Active sprints' Board, currently containing 90 tickets of type Bug, Task, Epic, Spike, Improvement, New Feature (no sub-tasks), in status'
Reopened, In Progress, Under Review, Ready for QA (No 'Done' or 'Closed' tickets)

The 'Backlog' view contains 1 active sprint and 2 inactive (future) sprints and a Backlog

On the 'Column Management' page (RapidBoard.jspa?rapidView=12&config=columns) there are 2779 issues showing as 'Done'

When trying to close the sprint it shows "0 issues were done" (consistent with the above) but then shows "511 issues were incomplete"

When I search issues by Sprint 520 issues appear, 429 of which imported in to the sprint from the last sprint as "Closed" (with varying resolutions, Duplicate, Won't Do, Done, Not Applicable, etc) from as far back as June 2016 that have been rolled through 17 different sprints

This affects the burndown chart, as the story points are not shown as released at the end of any sprints

I tried doing a bulk action to Close all tickets, but they still rolled over to the next sprint

I ended up selecting the extra tickets and setting their sprint to the empty string in a bulk action. They're gone for good now.

Clunky but it works.

Ha! 
That's great @Christophe L. 

Did you lose the historic information about which sprint they were originally a part of?
A small issue, if I can get rid of these 2 year old tickets

This would need to be done each sprint, in order to get a burndown, is that how you are managing it now?

Chris

I haven't looked at the history of the extra tickets, I'd imagine everything would be there.

I haven't had to do it again since but I'm keeping an eye on this type of tickets now.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

275 views 1 2
Join discussion

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