Time Estimation aggregates
Hello Jetbrains Community!
I currently have a question, which is kind of a follow-up to this thread here:
Given that I have an issue with a time estimate of 2d. I then create a sub-issue with an estimate of 1d. The parent estimate still says 2d because I manually entered the value. If I delete the 2d from the parent ticket it shows 1d of estimates from the sub-issue.
Is there a way to have the estimation work correctly (2d parent task + 1d child), without resorting to create an extra field which tracks the estimates for each task individually (and calculate the correct estimate with a workflow)?
Alternatively I could detect this situation with a workflow and automatically create a new parent to both to have a correct estimation again.
Are these the only ways to solve this problem or are there any inherent solutions that I'm not seeing? Or is this just the way it works and if I want estimates on both parents and subs, I have to deal with manually entering the correct values, like suggested in the other thread?
Any help is appreciated.
Please sign in to leave a comment.
Hi! When Time Tracking is enabled in the project, Estimation and Spent Time for parent tasks are calculated as the sum of the corresponding values for each subtask. So this seems to be working as intended. As another workaround, I guess you could also create a workflow that would copy the Estimation value of the issue whenever it becomes a parent and add the value to the estimation of its first subtask. If I understand correctly, the problem is with a particular case when initially the issue has no subtasks, so that might do the trick here for you, as well as the other workflow options you mentioned.
Thank you for your response. You are correct, the root of the problem arises when new subtasks are created after the original issue has already been estimated.
Let's consider a scenario where I have a task A that requires 2 days to complete. Now, I have a subtask B, which I delegate to someone else. Task B has an estimated time of 30 minutes and is assigned to a different person. With the suggested solution, I would end up with a total estimation of 2 days and 30 minutes for the entire task A, including the 30-minute subtask B. While the overall estimation in the parent ticket A is correct, the estimation for the individual subtask B is inaccurate.
So as I understand it, at the moment, there is no other way to solve this problem except by implementing a custom workflow?
Not sure why that is, can you please clarify? I would assume that the estimation for subtask B is accurate in the case you describe (as it is simply the value you enter within this subtask).
In general though, there is no way to modify this behavior, so you are right about the need to create a custom workflow if you would like it to work otherwise.