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?
I do have two status "won't do" and "done" when tasks won't be done for x reason we flag them as such but the column of won't do is not the right-most column because that is "Done" so the items on won't do are never removed from the sprint and keep moving forward to the new sprint. Any suggestion to resolve this?
Map your "won't do" and "done" status into the last column on the board.
"won't do" is not the usual way to do the end of an issue. It is best supported by have a "done" status, and resolving the issue with a resolution of "won't do", not having a separate status.
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
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?
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.
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