Sprint Burndown Chart - Remaining Values

[Brent Hetland]

Hi,

Why do the "Remaining Values" not update, until I move a Task to "Done" status?

If I have a task that is initially estimated to take 16 hours, and then I set the status to "In Progress", log 4 hours on it one day, log 3 hours on it the next day, I'd expect the Burndown chart "Remaining Hours" to reflect the 4 hours and 3 hours. But it doesn't.

It doesn't reflect the hours logged, until I change the status to Done.

That makes no sense, since all of my tasks in a sprint could be "In Progress" with just an hour work remaining, yet the burndown chart would show all of their original estimate time remaining.

Perhaps something needs to be configured differently for it to work the way it should???

Thanks, Brent

[Taranjeet Singh · Accepted solution]

@Brent Hetland You may not have selected the Estimation and Tracking Statistic correctly in your JIRA project for your use case. Please refer to this Atlassian document to see how you need to set them so that when you log time on your issues, then the Burndown chart shows the partial burndown (the number of hours currently used and remaining each day): 

https://confluence.atlassian.com/jirasoftwarecloud/configuring-estimation-and-tracking-764478030.html

[Brent Hetland]

Thanks! That is what I was looking for.

Sorry for the novice-level question! I'm not the Admin of the board and we've just started using it...

Best Regards, Brent

[Judy Colonero]

I have a similar scenario:

On the burndown report for TP-60 it shows there is 2d 7h 15m remaining. 

On the actual story:  Estimated = 5h, Logged 4h, Remaining 1h -- this is correct.  

How can the report show that there is 2d+ remaining.  This is misleading to management who periodically reviews the sprint burndown report.  

It also states in the Event Detail of the Sprint Report:

"Remaining Time Estimate changed from 5h to 1h".