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
I am using Sprints in JIRA, and I have several tickets that have been released and closed. However, they still keep moving from one sprint to the next one each time I close a sprint. What makes the backlog and board quite unmanageable, in addition, is that the provided metrics from the software are not valid.
I was searching for help, but nothing similar to my situation. Might someone provide me some help? Thanks in advance.
In Scrum boards issues are considered complete once the sprint is completed if and only if they are in the right-most column of the board. If you happen to have a ‘done’ status in some other column they will not be considered complete when the sprint is closed.
Yep understood. This is a very frequent it’s not the most frequently asked question in the community. I do wish that it would become more obvious when creating a scrum board for the first time. Such as creating a board you could have a wizard or coach that would walk you through the process. Of course he would want to disable this once you become proficient. In any case I’m sure this will get you going. Have a great day, cheers!
@Jack Brickey what is the point of having multiple "done" states if you can't clear those tickets after a sprint closes? For instance, what's the "correct" workflow for a "done - won't do" state ticket after a sprint closes (especially if you dump all tickets into the next sprint in the backlog)?
Hi @Nina Djokovic ,
I am confused by 2 boards for one sprint. Sprints and boards have a 1:1 relationship. Could you clarify? Maybe you have a Kanban board defined such that it overlaps with your scrum board? If that were the case, issues in scrum board's right-most column define sprint closure not the Kanban.