Time estimates and spent time not propagating.
Hi there,
New user here so this could be a configuration issue. We've enabled time tracking in the relevant project settings and the fields appear, but assigning values does not propagate up to the parent issues. How do we fix this?
Shareef.
Please sign in to leave a comment.
Hi!
I'm Sergey from the YouTrack team.
Firstly, please make sure that not only time tracking is enabled in all the projects your parent and subtask issues are part of, but you also have the same fields selected for estimation and spent time calculations
In general, when you enable the time tracking, the estimation (the same applies for the spent time) is calculated the following way: the parent task's value is the sum of its subtasks' values. However, if you enter the estimation value for the parent task manually, the automatic calculation gets broken. The easiest way to get the automatic calculation back is to sum subtasks' values manually and add the end sum to the parent's value (so it will match the sum of subtasks' values).
If it still doesn't work as described, please share screenshots with the examples. Thanks.
So we have a single project and the time tracking is enabled as you have shown already. However, I have examples of parent issuses with sub-tasks that are just not accumulating either the Estimation or Spent time fields. And they also have not been manually overridden. The following example shows a “?” in the time field where the 3 sub-tasks all have valid Estimation values.
Shareef Jalloq your screenshots shows ‘Depends on’ links. As I mentioned, time entries aggregation is done based on parent → subtask of links. Please refer additionally to our time tracking documentation to learn more about how it works: https://www.jetbrains.com/help/youtrack/cloud/time-management-tutorial.html#track-estimations-spent-time.
Looks like it's still happening:
Each of the sub-tasks have time estimates and they're just not propagating up.
Thanks for your response.
Please add the sum of the subtask's estimate values to the parent issue once. If the parent's value was adjusted manually at some point, it should re-enable automatic recalculation. After that, test it again by updating the value in one of the subtasks and see if it reflects on the parent issue.