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 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?
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.
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.