How do I sum the child tickets of an Epic

[Carlos Barros]

I am creating an automation called Teste_Calculo and it is configured as follows:

• Changing the Sprint fields,

• I create the variable varSomaEstimativa:
  lookupIssues.timeoriginalestimate.sum
  where the item type is equal to Task,

• For the Parent,

• I edit the Original Estimate field with varSomaEstimativas.

The Original Estimate field of PRO-5459 is updated with 120h, but the Original Estimate field of PRO-5448 (Parent) is not being summed.

What could be incorrect?

[Matteo Vecchiato · Accepted solution]

Hi @Carlos Barros

Maybe this article can help: https://community.atlassian.com/forums/Jira-articles/Calculate-the-sum-of-original-estimates-of-all-issue-types-to-an/ba-p/1660572 

Regards

[Carlos Barros]

Thank you for the workflow.

I completed the entire configuration, but it didn’t work.

In the log I see:

JQL Condition
08/18/2025, 1:52:49 PM

The following tickets did not pass the condition:
PRO-5458

Thanks

[Matteo Vecchiato]

Hi @Carlos Barros

For activating the automation, a change must be done in PRO-5459. The parent (PRO-5458) doesn't meet the condition of issue type = task.

Regards

[Carlos Barros]

Hi @Matteo Vecchiato 

Can't I create a rule for a child type Task and a parent type Epic?

I need to add up all the hours logged in tasks in epic

Thanks for your help.

Regards,

[Lígia Zanchet]

Hi Carlos,

It’s great to meet you!

Thank you for the screenshot and information.
The issue seems to be with the second condition in your automation rule. If you want your rule to trigger from Task PRO-5459, that task becomes your “triggered issue.”
However, when you use a branch in your automation, the context shifts to the Parent (PRO-5448).

Here’s where things get tricky: the condition if Epic Link = {{issue.key}} is checking whether the Epic Link field in the Parent matches the Parent’s own ID. That comparison will always fail, since a task’s Epic Link would never be its own key.

My recommendation? Remove that condition and give your rule another test. This should help your automation behave as expected.

Thank you, have a nice day!

[Carlos Barros]

Hi Lígia,

It is a great pleasure to meet you!

Thanks for your help.

I changed the workflow, but now I am recieving the error PRO-5458 (Specify a valid value for Original estimate (timetracking_originalestimate), Specify a valid value for Original estimate (timetracking))

Thanks again, have a great day!

[Carlos Barros]

Hi Lígia,

It is a great pleasure to meet you!

Thanks for your help.

I changed the workflow, but now I am recieving the error PRO-5458 (Specify a valid value for Original estimate (timetracking_originalestimate), Specify a valid value for Original estimate (timetracking))

Thanks again, have a great day!