-
Bug
-
Resolution: Answered
-
Medium (View bug fix roadmap)
-
None
-
None
-
None
-
None
-
GreenHopper (v6.1.3.1) JIRA (v5.0.2#725-sha1:5735107)
The Board's Estimation/Time Tracking option is set to 'Remaining Estimate and Time Spent'
1) Create a subtask of a story in the active sprint
2) It's estimated time should be 10 hours
3) Log 5 hours
At this point the burndown should correctly log 5 hours spent and 5 remaining
4) Resolve the issue (leave 'Remaining Estimate' set to Adjust automatically and don't log any additional time)
The burndown chart will not remove the last 5 hours from 'Remaining Estimate' even though the JIRA issue correctly resets the remaining time to 0h
The workaround seems to be to either log work when closing an issue, or manually set the remaining time to 0 by logging work before closing the issue. Once the issue is closed, it's a bit more work to fix the burndown chart (assuming you know which issues were improperly closed)
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-7704] Burndown doesn't adjust remaining time when closing a task
I think you'll need to open a ticket with support to reproduce this issue.
The most likely cause of this is when the issue history doesn't correctly contain an entry showing the remaining estimate moving from 5h to 0h (you can check for this in the 'All' tab of the Activity section of the view issuepage). JIRA does not normally 'reset the remaining time to 0h' when an issue is resolved but many users add a post function to the workflow to do so, the most common cause of this problem is when the post function is incorrectly configured to occur after issue history has been written.
Thanks,
Shaun
That was the problem! Thanks for your help