Sum up the original time estimate Field

[Omri Zeman]

Hey I wanna create Automation that In Jira cloud automation

Sum up the original time estimate Field from sub-task to story and from story to epic.
The automation needs to work in create, edit.



In the edit i write this:

{ "fields": { "timetracking": { "originalEstimate" : "{{lookupIssues.timetracking.originalEstimateSeconds.sum.divide(60)}}" } } }

[Bill Sheboy · Accepted solution]

Hi @Omri Zeman 

What is not working as you expected for the rule shown?  Perhaps also post an image of the audit log details for the rule execution and the rule details at the top to provide context. 

Rules like this trying to update multiple levels are typically recursive, for example allowing an update to a Subtask to update the parent Story, which then updates the Epic.  This may be done by carefully enabling and then testing with the rule option:

Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule.

Next, you describe the "automation needs to work in create, edit."  That is not possible with one rule.  Instead you will need at least two rules, triggered on Issue Created and Field Value Changed for time tracking.

But that is still not all the cases...so please consider which of these you want to handle to decide how many rules are needed and their structure:

• When an issue is created with a Parent and Original Estimate, update the Parent
• When the time tracking changes for an issue with a Parent, update the Parent
• When an issue with a Parent is deleted from Jira, update the previous Parent
• When an issue changes its Parent, update both Parents
• When someone manually changes the Original Estimate in an issue with child issues, recalculate the field based on the child issues
• etc.

Kind regards,
Bill

[Omri Zeman]

Hey Bill yes here is the audit about our automation:
It was when we add value to the sub-task

[Omri Zeman]

Yes you right we will need more automations for this,
but for now we wanna know how to this on the "Edit"
for example I have task with 
Original estimate = 5m

and when I update the sub-task to 
Original estimate = 5m 

I wanna that the task Original estimate = 10m
Do you know what we need to change in our Rule for this to succeed?


But for sure lets start with this one:

• When the time tracking changes for an issue with a Parent, update the Parent

[Bill Sheboy]

Thanks for that information, and...

Based on the rule image you show, the Edit Issue action is trying to modify the Original Estimate field twice: once from the field dropdown list and once with JSON.  Only one method may be used at a time for a specific field.

I recommend removing the JSON and using just the sum from the Lookup Issues result directly to set the field (using the dropdown selection).  You may need to add the units of measure at the end of the value.

[Trudy Claspill]

Hello @Omri Zeman 

Is this Automation not working as you expect?

What results do you expect?

What results do you get?

What information is provided in the rule execution Audit Log?

[Omri Zeman]

Hey for example I have task with 
Original estimate = 5m

and when I update the sub-task to 
Original estimate = 5m 

I wanna that the task Original estimate = 10m

I also attach the audit problem from this automation thanks.