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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Sum Up Original Estimations - Jira Automation

So I currently had to build a lot of workarounds to get the sum of all original estimations into the Epic. But it can lead to errors, when I clone a task and add it into another epic (it is an edge case, I know, but I still want to fix this :D) Is there an easy way of doing this?

Something like:

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


"{{#=}}{{issue.subtasks.Original Estimate.sum}} / 60{{/}}"

for Epics too? 

It is working for stories with sub-tasks, but not for Epics. 


Best Regards



1 answer

Hi Dennis. Sorry to disappoint, but the short answer for you is this: you'll need to pay for a Jira add-on to do this.

The basic set of JQL and Automation features in Jira (even for the Premium plan you have) do not support the aggregation of data from Stories to Epics in arbitrary ways.

As you've discovered, there is some support from Sub-tasks to Stories. So it seems like it would follow that you could sum things up from Stories to Epics. Again, short answer: nope.

I wrote this rant last month about why automation in Jira is incapable of currently doing this. Many of us have tried to make this work, and failed.

There is a link to a related bug/suggestion in my rant, and you can vote for that to get fixed.

The only other approach I know is to explore the Atlassian Marketplace for an add-on to Jira that you can afford that will enhance your queries and operations on the results. That can get you to computing the result you need. But I don't have enough experience with them -- particularly how to use them within automation -- to help further. The instances I manage include minimal add-ons.

If you find a solution that does work for you, please share it here for others! Best wishes.

Hey Mykenna Cepek,

then I need to go with my workaround. It is almost possible, when you use the values fieldChange.from and depending on the Trigger Time-tracking (it's called Zeiterfassung in german, I can't really say how they translated it :D ).

With a lot of if and else-if I almost got it. I can show you my Automation if you want to. Maybe we can work together on some workarounds :).

But yeah, it would be cool to have something like for tasks and subtasks. Because the workround is error prone


Best Regards, 


Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you