Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to sum the original estimate from children to parent?

Gil Levy June 30, 2025

I'm trying to use Jira automation to go over all the child issues of an epic that are not in Done category and sum up their original estimate and edit the epic's original esimate with the sum value.

 

This is my rule:

{E0CDAD42-24EC-45AB-8F30-632908C1D594}.png

2 answers

0 votes
Trudy Claspill
Community Champion
June 30, 2025

Hello @Gil Levy 

My first question would have to be "why"? What problem are you trying to solve?

It is great that you provided a screen image of the rule. That is helpful. However, you haven't told us anything about the problem you are encountering. What is the output in the rule execution Audit Log? What are the results you are observing that don't match your expectations?

I can state that your use of the "For: Parent" branch is incorrect. What that tells the rule to do is look for the Parent of the trigger issue and execute some steps against the parent. Your trigger issue is your Epic, so you don't need that branch at all.

Remove the branch and see if that resolves whatever problem you are encountering.

If it doesn't, please provide more information about the results you are observing and the output in the audit log.

0 votes
Walter Buggenhout
Community Champion
June 30, 2025

Hi @Gil Levy,

There's a lot of questions that could be asked about your use case as well as your automation rule - such as:

  • where are you manually triggering the rule from? If you only allow the rule to be triggered from epics, then the Issue type equals epic condition is not necessary.
  • If you're triggering the rule from an epic, then the for parent branch does not make sense, since you already are at the epic work item.
  • The JQL to retrieve the child items for an epic should use Parent instead of "Parent Link" 

With that in mind, maybe you can already proceed to some extent. If not, please provide more details about where you are stuck and/or share details from the audit log so we can better understand where you are and what pieces of the puzzle are still missing.

On a side note: if you are on a premium plan, you can see the estimates across the hierarchy roll up to parent issues in a plan (advanced roadmaps).

Hope this helps!

Gil Levy July 1, 2025

Hi. Thanks for the reply.

The 1st bullet point was just a safeguard so people won't run on other issue types, but I get your point.

The 2nd bullet point - that was the main issue. Removing that resolved everything.

The 3rd bullet point - Seems that it's working with "Parent Link". Is the parent link being deprecated?

 

As for the side note: I have the premium plan but I'm not able to see the estimates as you mentioned. Can you please share a screenshot where do you see that?

 

Edit: Trying to make this rule to work also on subtasks and it's failing. Example: I have an epic with two tasks and one task has a subtask.

 

Epic: 2d 6h (sum of Task 2 + Task 1)

Task 1: 6h (2+4)

subtask 1: 2h

subtask 2: 4h

Task 2: 2d

 

I was hoping that the rule will work given I have this JQL ("Parent" = {{issue.key}}) and (status != "Won't Do") on subtasks and then on the tasks and then on the epic.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events