Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,639,531
Community Members
 
Community Events
196
Community Groups

Remove Closed Tickets from a Completed Sprint and Released

 

Hi,

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.

1 answer

1 accepted

1 vote
Answer accepted
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 02, 2021

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.

Then it might be this the case, but I did not read anything about this limitation with the "right-most column". I just changed it, I will keep you update if this works. Thanks a lot for your quick reply =)

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 02, 2021

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!

Like # people like this

It works! =) Thanks a lot for your help @Jack Brickey!

@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)? 

What happens in case when we have 2 boards for 1 sprint? Which right column is considered as Done?

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jul 27, 2023 • edited

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.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events