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.
Hello,
Recently, we've changed our workflow for all our projects. Now all done issues appears on the backlog of our projects, while they are allocated to previous closed sprints. How could this happen and what should I do to remove them from from the backlogs?
Hopefully someone can help me!
BR. Kelly Koolen
Hi @Kelly Koolen ,
JIRA Software does not display issues from the last column of the Scrum board configuration in the backlog section. If your closed issues are not mapped to the last column of the board, then they would be displayed in the backlog.
Thanks for anwering. That might be the problem.
But then my question: how to handle 'cancelled' and 'pending' statuses? We do need to separate them by column. So, one column for 'cancelled' and one column for 'done' issues. We need do put 'cancelled' at the last column in order to close a sprint, otherwise that don't work out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Kelly Koolen ,
You can map two statuses to a column. You can craete a column called Completed and map both "Cancelled" and "Done" statuses to it and make sure that the column is placed at the right most.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have items in status Done which is mapped to the last column of the board, but these still appear in the backlog. Is there some other setting that is overriding the behaviour described in this answer as that is what I would expect to happen.
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.