Burn down report not showing remaining work

[Ralph Esslinger]

I am using the built in time tacking. I have a sprint with one task.  This task has an estimate of 4d.  every day I log work and the remaining time on the task deceases as expected.  The estimation field is 'Time' but the burn down chart does not decrease.

Just below the remaining work it shows 'Number of story points left to complete this sprint'  How do I change that to show the time remaining.  I am not using story points. 

I would like to see the overall time remaining reduce every day where I have logged time or changed the remaining estimate.

[Nic Brough -Adaptavist- · Accepted solution]

Burn down only happens when an issue is done, it's not looking at partially complete items.

In this case, you'll get a staight line drop of the whole estimate when you finish the single issues.

If you want a progress report, rather than a burn-down, then look to the progress reports (the burn down does have a cheat where if you're estimating on story points or something else, it will show time logged on the chart, but that is not the burn down!)

[Ralph Esslinger]

Thanks for explaining the limitation of the burndown report.  Where are the progress reports.  When I search for Progress report, the only result is the burndown report.

[Nic Brough -Adaptavist-]

It's not a limitation, it is working to show you what the burndown is, it's doing what it is supposed to do!

By "progress report", I meant whatever report shows you what you are looking for.  You'll need to explore all the reports in there.  I can't think of one immediately that would show you this, but that's down to me not needing one.  Sorry I can't give you more than that.

[Ralph Esslinger]

Thankyou for clarifying.  It seams like the only way to get it to work is to make many small tasks but this is very difficult to do as many of the small 2-3 hour tasks emerge during the task.  How could story points be used to achieve the burndown?

[Nic Brough -Adaptavist-]

Your instinct is right - the point of a burn-down is to show committed vs done in a sprint, and a sprint is usually made up of several stories of varying sizes.   

It doesn't really matter if you're estimating in time or story points, to see a burn-down in a chart, you'd need to be finishing each of them in turn so it counts them as done.  With only one issue in here, you're only going to see a single 100% drop when you close it.

It might be worth seeing if you can split your single-sprint item into a few pieces, although 2-3 hours a piece may be a bit too granular to be useful (I don't know your data, so I can't guess)