Time Remaining never reaching Zero on Burndown chart, even if end date is extended

[AlexS]

Hello,

We are seeing an issue in our hour burndown charts where at the end date, the time tracking is wildly inaccurate compared to the actual Remaining Time.

Thinking this may have been an issue where work was closed after the end date, we extended the end date till tomorrow, and the Chart still does not match the current information in JIRA.

We have 3 remaining tasks as overhang from the version, totaling ~20h of work, but the current burndown shows 351h.

Doing time analysis, checking the issue navigator or exporting to excel from the Version's little cog icon, all match our data in JIRA - but not the burndown chart.

The version info on the sidebar shows the following:

Time Estimate: 38 weeks, 4 days, 3 hours

Time Spent: 38 weeks, 2 days, 4 hours, 8 minutes

Time Remaining: 8w, 3d, 6h, 5m

Does anyone know what can cause this seeming permanent increase in the time remaining?

[sclowes · Accepted solution]

Hi Alex,

Probably best to log a support ticket on this one at https://support.atlassian.com, they should be able to help you diagnose where the missing hours are.

Thanks,
Shaun

[Evan Hart]

See here and here for a better explanation of this intended behavior.