Time tracking; Solving a story doesn't remove remaining time or solve subtasks?

[Lars Hahus]

If I have a story with 10 subtasks with individual time estimates, shouldnt solving and closing the story just shave those time estimates off and mark all subtasks as solved?

The time tracking reports gets really weird as it pays no attention to weather or not a task is closed, only that it has remaining time from the initial estimate.

Do we really need to always adjust the remaining times to "0" for the time tracking reports to be useful?

Shouldn't time tracking ADD the time that one task has gained by being solved faster than the original estimate to the overall remaining time estimate of a version?

[darylchuah · Accepted solution]

Hi Lars

Referring to your issue, there is already an improvement request being raised : https://jira.atlassian.com/browse/JRA-8946

Please feel free to vote on it to increase its popularity and add yourself as watcher in order to receive any latest updates from the developer and feedback from other user that is facing the same issue.

Cheers :)

[Gebsun]

Log Work Utilities add-on allows to clear remaining estimate on issue close/resolve without a need to modify workflow: https://marketplace.atlassian.com/plugins/com.gebsun.plugins.jira.log-work-utilities/server/overview

[Joseph Narai]

We also need the same issue solved!!

[Tobbe]

Hi

We are also facing the same issue. when a subtask has been closed it will still show time remaining in parent issue. If a subtask has been closed then all time estimated on the sub-task should be removed from parent time remaining.

The result otherwise will be that you can end up will all sub-tasks closed but on the parent task it will look like you still have time left before it can be closed.

[hwijnveen]

Hi Daryl,

the improvement you refer to is more about automatically closing sub-tasks when a Story is closed. Personally I would not appreciate this; rather have it the other way around (which is already possible, isn't it?).

The point here (AFAIK) is about setting the remaining Estimate to 0 when a subtask (or any other issue type for that matter) is resolved or closed. Something that would be very practical in my situation.