What workflow state triggers a Story Point being burned-down?

This question is in reference to Atlassian Documentation: How do Story Points get burnt down and reflected on the Burndown Chart

We're tracking the transition of code changes from Dev to Prod with two different workflow states, both of which have a Category of "Done". When an Issue moves from 'Validating On Dev" to "Validated On Dev" I would like the Story Points to burn down at that point, but I'm observing that it only occurs when I move issues to "Published" (which is another "Done" status available from "Validating On Dev"). 


We have a "Close Early" status as well (also in the "Done" Category) which also burns down Story Points. And both "Close Early" and "Published" have transitions to other statuses. I'm unclear on what makes "Published" and "Close Early" burn down Story Points, while "Validating On Dev" does not.


2 answers

1 accepted

1 votes

It depends on the column mapping. Statuses that are mapped to the last column on the board will contribute to the burn down. If you add "Validated on Dev" in the last column, burn down will happen when the story reaches that status.

Gah... excellent I didn't think to look at the columns.


You can't add addition start-state (blue) or end-state (green) columns, but you can add as many intermediate-state (yellow) and I had "Validated On Dev" in a 2nd yellow column. I moved it to the green column and all is well.


What if there are 2 boards in a project for 2 different views and in one board Validated On Dev is not the final column and on the other, Validated on Dev is mapped to final column with Done?

I have TODO > IN PROGRESS > PREPARE UAT > UAT > AWAITING QA > DONE, I want to burndown at AWAITING QA i.e. once UAT is completed. In this case, my AWAITING QA is the same situation as Validated On Dev.

The JIRA Burn Down charts will burn on two configurations, burned down if the "Issue Closes (Resolution field has a value)" or by "Logged Work". You have the first option set and "Published" is populating the resolution field that's why there's a burn down being detected.

P.S. The configuration for this can be found on your Board, click on "Configure" on the top right section, then click on the "Estimation" tab. In the "Time Tracking" section, select "Remaining Estimate and Time Spent"

Reference: https://confluence.atlassian.com/agile066/jira-agile-user-s-guide/configuring-a-board/configuring-estimation-and-tracking


Thanks for the feedback.
  1. No, the status "Validated On Dev" has a value for the Resolution field.
  2. I don't want to change to "Remaining Estimate and Time Spent", I only want to use Story Points at the moment. Making that change is a question of process and what works best for our group and not a technical fix to get JIRA to behave as expected.

Thanks again!


Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,798 views 11 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot