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,457,545
Community Members
 
Community Events
176
Community Groups

Customise Burndown Chart to consider as Done a mid "Review" column

Hi all, 

 

i am trying to make a customisation at the Burndown chart. I have set all my boards with four columns. "To-Do", "Doing", "Review" and "Done". The Burndown chart considers as "Done" and drops the line in the graph when something moves to the "Done" Column/Status but in most cases the dev team has finished their work when issue moves to "Review" column. 

My problem is that in "Review" column is being created a bottleneck and this is not dev's team fault. So to have proper metrics for the progress of the dev team i need when a issue moves to "Review" column the burndown chart to lower and consider this issue as Done at least from dev team side.

Is that possible?

1 answer

0 votes

Hi @Vasilis Gennaris ,

a status, in order to be considered as done, should be placed on the last column on the right of your board.

Hope this helps,

Fabio

Hi @Fabio Racobaldo _Herzum_ ,

The issue I see here, is that it is now possible to set the `Done` category to more than one status (not necessarily all within the last column in the board). Therefore, the Burndown chart should consider all `Done` category statuses as Done and not only the last column.

Is there a solution for this ? I am facing the same kind of issue. My dev team is involved in the process up to the Code Review, but once the PR is merged, I consider their job done.

Therefore, I would like the Burndown chart to consider statuses like "Testing", "Pending Deployment" etc as Done.

 

Thanks

Leslie

Hi @Leslie Martinez ,

a ticket is considered "done" if the status is on the last column of your board indipendenlty from status category. Status category is general and not per project basis. Some statuses, that are global for the instance, could be considered as category"done" for some workflows and "in progress" for others. THis is the reason why Atlassian based the burdown chart on the board configuration. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events