Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

rollup original estimate at epic level

Is there a way (using Jira automation) to roll-up original estimates from Standard Issue Types to linked Epic?


I tried to use the formula {{#=}}{{issue.remaining estimate.sum}} / 60{{/}}

when issue equals Story and Value changes for Time Tracking

then for Epic update custom filed = {{#=}}{{issue.remaining estimate.sum}} / 60{{/}}

but it does not work.

2 answers

1 accepted

2 votes
Answer accepted

I did it as follows;

Created this rule for changing the Story Estimate when a sub task estimate changed

Screen Shot 2022-04-04 at 17.49.42.png

Action is: {{#=}}{{issue.subtasks.original estimate.sum}} / 60{{/}}


Created this rule for changing the Epic Estimate when Story estimate changes

Screen Shot 2022-04-04 at 17.42.57.png

In the last action step I used:

{{#=}}{{lookupIssues.original estimate.sum}} / 60{{/}}

Make sure you allow the first rule to trigger the second rule by setting;

'Allow Trigger' in the rule details of the second (Update Epic) rule

Screen Shot 2022-04-04 at 17.52.14.png

@Michael Marriott 

Thanks Michael for your solution. This is really helpful

@Michael Marriott is there a way to add to story estimate when subtask estimate changes?  For example, if story estimate is 2d, and a subtask is added to story with a subtask estimate of 3d, then story estimate gets updated to 5d?  In your above example, story estimate gets set to 3d.

Hello @Nab Khan , 

Both these rules are triggered when the 'Original Estimate' field is changed in a sub task (updates Story) and a Story (Updates Epic if it exists). First rule will trigger the second rule if configured to do so.

If you 'move' an existing sub task to a Story then the rule will not trigger.

If you add a subtask to a story and then set the 'Original Estimate' the rule will sum all 'Original Estimate' fields for all sub tasks to the Parent task.

Any Original Estimate manually added to the Parent Task will be over-written.

Note; Automation can take time to fully complete all actions. In your example if you refresh the Story after rule completes execution you will see it will update to the 5d.

Hi @Michael Marriott ,

The rule does sum all 'Original Estimate' fields for all sub tasks to the Parent task, and overwrites the parent task 'Original Estimate' value with the sum. 

What I would like to know is if it is possible to not overwrite but append. 

For instance, if the parent task has an estimate of 5d and a new subtask is added with an estimate of 2d, can the original estimate on the parent task be set to 7d?

Hi @Nab Khan

You could store the current value in a variable before doing the calculation and then include the variable in the calculation. I wouldn't do that since you will continually accumulate. For example if you remove a sub task or adjust it's value then the roll up value will be wrong since you will retain the old value and add the new value for the same sub task.

@Michael Marriott 

Thanks for your feedback. Considering these complexities, i went ahead using python + JIRA REST API to read the summed up original estimates at standard issuetype level and after doing the calculation in code update the respective field value in the epic.

this helps avoid taking care of lot of scenarios like you mentioned in Jira automation

@Michael Marriott  you sir are a lifesaver! Just one minor adjustment: on the second rule's action math, an additional division by 60 was necessary.

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Aug 16, 2021

Hi @Vishal Biyani 

What problem are you trying to solve?  You note original estimate in your question, and then you show smart values for remaining estimate values.

If you need either of those things, please look at the links noted at the right-side of this post for earlier articles: Related Community content

And, to find the names of smart values which may not be noted in the documentation please review this how-to article:

Best regards,

@Bill Sheboy  Thanks for pointing this out. I have rectified this mistake. However, not able to meet the use case as detailed below

Under Epic, i have Stories, Task and Custom Standard issue time (say Use Case). 

We have created custom fields at Epic level
Field Name: StoryEffort
Field Name: TaskEffort
Field Name: UseCaseEffort
Field Name: TotalEffort
with the objective to rollover aggregatetimeoriginalestimate of Stories , Task and Use Case in their respective field and then sum up the total effort 
Under 1 epic i can have multiple stories.


When i use the below rule to populate StoryEffort, instead of summing up the aggregatetimeoriginalestimate for all stories, i get the aggregatetimeoriginalestimate for only the story for which the effort was updated.

Is there a way to write the formula such that i get some of all aggregatetimeoriginalestimate for all stories under an Epic, if the value changes for any 1 of the story.

i tried lookup issue as well, but it didn't yield any result.

{{#if(, "Story")}} {{#=}}{{issue.aggregatetimeoriginalestimate}} / 3600{{/}} {{/}}

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Aug 26, 2021

Hi @Vishal Biyani 

You may want to post your entire rule to provide more context.  Thanks!

If you look at the examples in the related contents posts, you will see examples of rolling up the values.  Generally this is done by either:

  • Iteratively adding to the epic's fields and the re-fetching the epic.  This can be slow and error-prone.
  • Repurposing a field like Story Points, by copying the Story's original estimate into the field, and then use Lookup Issues actions to more easily sum the values.

Best regards,

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events