Story point burn down

Dorothy Callahan

Good morning,

Currently, our board is set up with the following statuses above.  

Know before I ask this question that this is far from a process I support but continually comes up as a challenge from team.  They want the board columns to be as above but they want the story points to burn down when story moves to Code Review.  Unless I mis-interpret the documentation I've read, story points only burn down when the status is in the rightest most column.  Can someone share with me how I can maintain the board columns as above but have the story points burn down when moved to Code Review in workflow.

 

Thank you.

 

Trudy P Claspill

Hello @Dorothy Callahan 

The short answer is you can't.

Story Points will burn down only when the status is in the right most column.

This is based on the concept that the burndown is tracking completed work. If the work in the columns to the right of Code Review is required for the tasks to be truly done, then it would not be proper to burndown the points until the task reaches the Done column.

It sounds like you're in a situation where developers want to show their work is complete, even though the work can't be "accepted" until the QA and deployment work is complete.

A way to do this in Jira is to have the work up to Code Review tracked as one task, and the work after Code Review tracked as a separate task. You could even still have them on the same board, though you would either need to use more generically named statuses, or combine the existing statuses into columns so that Code Review is in the right column and Ready for QA and Ready for Deployment are in columns to the right. Or, you could set up separate boards for the two different groups of work.