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,460,380
Community Members
 
Community Events
176
Community Groups

How to fix Velocity chart and have Archive Status for backlog items?

I wanted to remove certain backlog items which are not planned yet but can be needed later . I created new Archive column / workflow by using done category . I moved all as of now unwanted backlog items to Archive column . In my last sprint due to additional Archive column Sprint Velocity chart went 0 for all the previous and current sprint . 

Screenshot 2021-07-16 at 11.36.25.pngScreenshot 2021-07-16 at 11.36.39.pngScreenshot 2021-07-16 at 11.44.35.png

1 answer

0 votes

My guess would be that your "archive" status is not in the last column on your board.

The last column of the board is for issues that are "done" and can hence be burned down on (commitment met)

I don't actually think that's the root of the problem though.  I think it's how you're thinking of this "archive" status.  Scrum and Jira at their heart really only have two settings for an issue - "It needs attention" and "it's finished with and does not need any more doing about it".  Jira looks at the resolved field for that - if it's empty, it needs attention, if it's filled, it's done.  The boards see the last column as done.

So, the first question is whether your archived issues are done or not.  If they are done with, fine, put the status in the last column, make sure they are resolved by setting a resolution and forget them, as they'll never need attention again.

If they are not done, then you have to move on to the question of whether you want them on the board or not.  From what you've said, I think you want them to be not done, but also not appear in the backlog.  As the backlog is also the board, they're built from the same selection of issues, I think what you should actually do is drop the status off the board completely, so that archived issues won't show at all.  You can do this by adding "and status != archive" to the board filter, or by not mapping the archived status in the board columns.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events