Time spent field in burndown chart is incorrect and is greater than the expected value

[Binoy Francis]

Hi,

The remaining estimate of issues are showing incorrect in the sprint burn-down chart.
For example: issue A and B have remaining time estimate as 100 and 160 respectively.
This is shown correctly in the time tracking fields and the history data of the issue.

But when we check the same issue in the burndown chart of the sprint in which the issue exist, the remaining time estimate of the issue becomes A-200 and B-320. There are also some other issues with more than 2* value in burndown chart.

More points -

-Estimation Statistic is based on Story points

-Enabled "Remaining Estimate and Time Spent" as Time tracking

-This affects random tasks. Always the case is the remaining estimate value will be higher in burndown chart.

- Adding subtask in affected issue cause the issue to be resolved.

Attaching screenshot for more reference.

[Binoy Francis]

[Steve McAfee]

I can easily reproduce this but it is sort of random. For me it happens when the issue moves to done. Usually when this happens the time remaining is fully deducted to zero. Sometimes it skips that deduction entry. Makes the feature pretty unusable.