Time estimate field behavior for tasks with subtasks
I'm trying to understand how time estimation field works for parent issues when it is set/modified for subtasks. So far, it looks like this:
1. If I don't set estimate for parent issue, and add a subtask with set estimate, it'll add to the parent issues's estimate. Similar for removal of subtasks.
2. I I don't set estimate for parent issue, and modify time estimate for a subtask, it it reflected in the parent task.
3. Once I do any modification to estimate of the parent issue (including setting it to "?" again), no modifications and additions/removals affect this estimate.
Is the above correct? If it is, is there a chance for me to reset the value in the "Estimation" field and make it track estimates from subtasks again? My usecase is simple: I have a couple of high-level tasks which hadn't been split into subtasks yet, but for which some kind of estimate is available. Once I start to make a detailed plan for the task, I split it into several subtasks, for which I enter their own estimates. By that point in time, the estimate on the parent task no longer makes sense - but I can't reset it, or otherwise make it match the sum of estimates of child tasks.
Please sign in to leave a comment.
Hello Victor,
this is a known issue with broken estimations aggregation, it happens when you change the field value in the parent task manually. Sorry for the inconvenience, we're working on a fix already.
Right now there is workaround to get time estimations working again in the parent task. You need to calculate all the time estimations in all subtasks manually and then change the field value in the parent task to this calculated value. After that, if your calculations are correct, the estimations aggregation should start working again.
Hello Liubov,
any update on a resolution for that issue? I have been trying the workaround you suggest for the simple case where there is only one subtask.
I set the parent task to 1w when the subtask is 2w. Then I change the subtask to 1w and to 2w again but the parent task doesn't update to reflect the expected 2w.
Guilliaume, as for the workaround, you need to calculate the aggregated value for the parent task and put it into the field manually, then the aggregation should start working again. For example, if you have one subtask with the estimation of 2w, you need to put 2w into the estimation field of the parent task.
The issue in question has already been resolved and this issue shouldn't happen again. Which YouTrack build are you using currently? You can check the build number in the lower-left corner of any YouTrack page.
Hi Liubov, thank you for your prompt reply.
I am using youtrack in cloud, version is :
I did try what you suggest as I understand it and still do not see the aggregation working again. I am happy to grant you access to our youtrack instance if needed to reproduce the problem on your side.
Guillaume, could you please submit a support ticket and provide the name of your InCloud YouTrack instance + the IDs of the tasks that this problem concerns?
You can either use the link on the top of this page to submit a ticket or write us to youtrack-feedback@jetbrains.com
Thanks.
Thank you, I just submitted a request from my account.