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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have completed our sprint and closed it. However all the 17 Done jiras in the last sprint are appearing in our new sprint.
All the Done tickets have the done tick next to them.
How do I remove them so they don't appear in the next sprint?
Is the resolution set to resolved on the issues that have a status of 'done'?
It might be an issue with your workflow.
Normally when you close a sprint you will be prompted to move any remaining tickets that are still in progress to the next sprint (or back to backlog). This works based on resolution rather than status though.
If you scroll down to:
'Setting the resolution field'
Here
https://support.atlassian.com/jira-cloud-administration/docs/work-with-issue-workflows/
There is an explanation that should help.
Thank you, I moved the Done column to the end of the board and this seemed to sort it.
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Stuart Capel - London ,
I figured out that, since i have a very similar issue, i'd post my question here:
I have tickets that appear to randomly just jump into the next sprint, despite
a) having a set resolution,
b) having the correct status, that is mapped to the very right column of the board,
c) being basically the same as other tickets that did not get transferred into the next sprint.
So what i want to say is: I have two almost identical issues, same issue type, same resolution amd same status. One gets taken into the new sprint, the other does not.
Can i consider this a bug? I have never had this problem before, so i am a bit confused. It does not happen very often, but it kind of messes up my team's metrics.
Thanks in advance
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.