Burndown Report is not reducing Remaining Estimate when time is logged.

Jon Platt
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 7, 2024

In my Burndown Report I see lots of entries like "4h logged, Remaining Time Estimate changed from 8h to 8h". The hours logged vary of course, but the Remaining Estimate doesn't decrement. If I look at the Estimate tab in the Issue I do see that the remaining time is accurate so it appears to just be an issue with the report. Any ideas?

3 answers

0 votes
Danut M _StonikByte_
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 9, 2024

Hi @Jon Platt ,

For the burndown chart to work based on time estimates, ensure that your agile board has Time tracking enabled.

image.png

Then, make sure you run the Sprint Burndown Chart Report by Remaining Time Estimate. 

If this does not help, you could try the Burndown Burnup Chart gadget offered by our Great Gadgets app. This gadget works with any type of estimates and can include the sub-tasks in the estimation. 

See also https://community.atlassian.com/t5/App-Central/Tracking-an-agile-project-that-uses-time-estimates-with-Great/ba-p/1699994 

Hope this helps.

Danut.   

0 votes
Matt Parks
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 8, 2024

Silly question, but is the Burndown Chart configured to use Remaining Estimate? Even if that is what your board is configured to use as the Estimation value, the Burndown Chart can use a different value.

Given that you said that the 'Estimate' tab shows that the remaining estimate is accurate, I am assuming that you're using Remaining Estimate as the Estimation on your board.

0 votes
John Connolly March 7, 2024

Hi @Jon Platt I will admit firstly that I don't use time logging and so take some of what I have to suggest with a pinch of salt...I'm sure someone will correct me if I am wrong.

Burndown charts typically burn down based on 'Done' on 'not Done'.  I like to understand this as you don't get the credit for the story/issue until the business value is released from it. If something is just 50% complete, how much business value can we get out of it?  So that might be your first problem.  For an issue with a 16h estimate, it can have 16h of time logged against it, but it's not done until it's moved to the Done column, and only then would it typically show up as a decrease on the Burndown chart.

There is also a Time Tracking report you may also want to have a look at, and Plans (was Advanced Roadmaps) can render a progress bar based on logged hours - as alternatives ?

 

 

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events