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.
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"
Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events