Hi,
I hop everyone is fine. I have created two custom fields for QA estimates and Dev Estimates. When I enter the values in these custom fields, it shows the of these two fields in Original Estimates. This works fine for me.
The problem occurs when I create sub-tasks under the story. For e.g. I have created two sub-tasks like 3.1 and 3.2 under the main story Test 3 ....both of these sub-tasks have custom fields and when I enter values in these custom fields it updates the original estimates accordingly.
I want those sub-tasks original estimates fields to sum up and show the updated value in the story original estimates.
Let me show you the SS of my main story and sub-tasks
This is my story and it contains 2 subtasks.
Here is my sub-task 1 with original estimate showing the sum of custom fields QA Estimation and Dev Estimates which is perfectly fine.
Here is my sub-task 2 showing original estimate of 2h ...1 hour each from custom fields.
Now my total sum from these sub-tasks is 7 hours. I want these 7 hours to reflect in the original estimate of the main story.
I want to do it through automation if possible. Please, Anyone?
This will be a great help if anyone provided me with the solution. Thanks.
You can try to use this automation rule:
- When: value change for Time Tracking
- If: issue type is subtask
- For: Parent
Edit issue fields Original Estimate (smart value: {{#=}}{{issue.subtasks.original estimate.sum}} / 60{{/}})
I hope this helps!
Let me know if you have any other questions.
Regards,
Y Dang
@Y Dang_Candylio - Thank you for your reply but it doesn't solve my problem. Maybe I didn't explain my problem clearly. I am using number custom fields in the sub-tasks. Also, I have changed the default unit for time tracking to hours.
Also, field value should be either QA estimation or QA estimates that changes and not time tracking.
Maybe we need to adjust the formula like don't enter 60 in the formula, I don't know. Please let me know if you have completely understood my problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Batsheva I Could you please show the details of "IF"-step condition? (like you publish it for that step)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Y Dang_Candylio @Batsheva I , I tried your solution but it's not working for me. Getting an error. Could you please help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
me too...
Could you please help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The only difference I see between our versions is that I used an "IF" for the comparison and you used the "Issue fields condition", but that shouldn't matter.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.