Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Our burndown is not reflecting work that has been marked as "Done"

Scott_Stephan
Contributor
March 10, 2020

Hi all,

 

Yesterday we realized that our burndown has stopped tracking work that is done. The line is flat. We definitely have work that's marked as resolution status "Done" and that work had Story Point Estimates on it.

To try and fix this we went to that work in the "Done" column and changed the SPE to 0. The burndown remained flat. In essence, we cannot get Jira to acknowledge that work is being completed.

If we add work, that is reflected in the Burndown. Weirdly, if we add a story called "Test" w/ a 10 pt SPE, we see the burndown go up 10 SPE. If we then mark that work as DONE and change it's SPE to 0, the burndown does NOT go down.

Additionally, in the history I can see the resolution clearly being marked as 'Done' and 'Done' is our right-most column on the Kanban.

Clearly we're misunderstanding something. Can anyone help?

A 10 pt test task

backlog.png

The Burndown Scope Log- You can see it get added, but not removed
bd_log.png

The burndown- Again, you can see the scope increase on "To-Do", but never

decreasebdown.png

The task history that shows the reduction in SP

taskhistory.png

1 answer

0 votes
Randy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 10, 2020

looks like a bug as you've checked and verified the configuration.  try opening up a ticket with atlassian support. 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events