I LOVE(d) the burndown chart in the "sprint insights" section of the board.
recently, it has stopped considering the "green" states to be "done." The impact: When I move a ticket into the first of our "done" states, "ready for demo," the burn down no longer burned, so I have to wait for the ticket to go to fully Done. The issue is that we consider the ticket devdone at ready for demo instead of production release since there are stakeholders who help guide our release schedule, causing artificial delays and meaning I will never burn down at the end of the sprint, even if the code has tested clear.
I need to have that burndown consider a ticket burned sooner so I can measure what I can actually measure of the team instead of having an artificial block with the production release.
What do I need to change to get it set back to burning down earlier? I can't find a control for it anywhere :(
Thanks!
Hi @Kat Crawford -- Welcome to the Atlassian Community!
Would you please post an image showing your board configuration, with the status mapping to columns?
Jira Scrum boards (and burn charts) consider an issue "completed" when it is in a status mapped to the right-most column of the board. The status category (which shows the green color you observe) has nothing to do with completion detection.
From what you describe, there are multiple status values, and perhaps one you consider as "done" is not mapped the the right-most board column.
Kind regards,
Bill
that is correct. I decided to expand the back half of the board, but if it is the right-most, I broke it on myself!
I wanted to do this the full board image, but the back half mapping is multiple greens. Looks like I will need to split it into 2 boards.
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.