You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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.
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.
Thank you Selina, I was battling with this too - we had a status "Duplicate" that was an end status in the workflow but items added to that kept rolling over to the next sprint. After your post I went and looked at the sprint board and yup, we didn't have "Duplicate" as a status in our final column :)
When you say "marked done", do you mean that they are in the last column on the board?
I have same problems where completed/done issues without child or parent issues gets moved through to next sprint. Completed/Done issues would be sitting on the Completed/done Column of the Board. And when I try to close the active sprint and start a new sprint, these lists of completed/done Issues gets moved through to the new active sprint.
My solutions is to create an automation rule.
When issues are transitioned to Complete/Done, the automation rule edit the Issue (specifically the SPRINT, it clears the sprint of the issue, as empty). Therefore these completed issues without any sprint, would be removed to the list in active sprint. So, at the end of the sprint, when I have to close the active sprint and start a new one, these completed sprint wont be there to start with anymore and they wont be moved to the next sprint anymore, as they don't have sprint in them anymore.
That's a clever "fix", but it completely breaks all your sprint reports and makes it pointless doing sprints.
You need to look at the issues that have this problem and your board configuration. You should not be clearing out the sprint field, you need to look at why you have not configured your board to work.