Somehow every new sprint, we have existing CLOSED tickets that get transferred to the new Sprint.
It is happening, when someone is closing old Sprint and opening new Sprint.
Have a look at one of these "closed" issues. Were they in the far right hand column of the board when the sprint was closed (look at the status at the time of closing and the board column mapping). Also, did they have one or more sub-tasks? If they do have sub-tasks, check the same for the sub-tasks - were they in the far-right hand column too?
Statuses "Closed" and "Resolved" are Unmapped in Board. Column "Done" contain tickets only with status "Ready for Release". Tickets had been closed before Sprint has been closed. Such tickets have sub-tasks and/or linked issues which are not "Closed" but "Ready for Release"/"Opened". Also i have found tasks which are in progress and moved to new sprint, those tasks contain sub-tasks in "Opened" and "Ready for Release" states, all those sub-tasks also automatically moved to new Sprint.
Right, that makes sense.
For an issue to be seen as closed by a sprint, it has to be in the right-hand column of a board.
Your closed and resolved issues, and the ones that have sub-tasks that are not done, are moved to the new sprint because you've told JIRA they are not done.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
@Rachel Wright (Jira Genie), @Billy Poggi (AUG NOVA, DC), and @Dana Jansen (Confluence Queen) are just some of the folks that lead one of the world's most active Atlassian User Group (AUG)....
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs