How to remove closed issues from the current sprint?

[Christophe L.]

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

[Nic Brough _Adaptavist_ · Accepted solution]

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

[Christophe L.]

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.

[Nic Brough _Adaptavist_]

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"

[Christophe L.]

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!

[Chris_Green]

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

[Christophe L.]

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.

[Chris_Green]

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

[Christophe L.]

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.

[marie_mitchell]

Hi @Christophe L. ,

Can you tell me how you did this please? 

"I ended up selecting the extra tickets and setting their sprint to the empty string in a bulk action."

I have an issue where tickets are automatically adding to the next sprint, sprint after sprint - sometimes pulling through on the sprint board but mostly not. No idea what the long term solution is but would be good to manage sprint by sprint for now.

Thank you,

Marie

[Christophe L.]

Hi @marie_mitchell 

IIRC, after selecting the relevant cases, I chose "Edit":

And then edited the sprint field:

Hope that helps

[marie_mitchell]

@Christophe L. - thanks for getting back to me. From where are you editing? I don't recognise the field in the screen shot!

Thanks,

Marie

[Christophe L.]

It's after you click 'Next' on my screenshot. There's a long page of things you can edit, just look for 'Change Sprint'.

[marie_mitchell]

Thank you @Christophe L. I may be that i don't have access, but i'll look in to this.

Thanks for your help,

Marie