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

Sum numeric values from a custom field

For better capacity planning we introduced the custom fields "FE-Estimates" and "BE-Estimates".

Both are numeric fields.



So now I want to sum all values from all stories into the same custom field within an Epic.

How can I do that?

I tried the following but it's not workingimage.png


2 answers

I just spent few hours trying to implement Bill Sheboy second proposal, and finally success! Hope this post will help someone to save time:


No rocket science, but you have to be very careful about parameter names and such.

Hi @Timur Khakimyanov -- Welcome to the Atlassian Community, and well done!

The part I find interesting about your web request, custom data is passing the entire {{lookupIsssues}} smart value rather than parsing the keys/id values out into a CSV list, such as: {{#lookupIssues}}{{key}}{{^last}},{{/}}{{/}}

Looks like your version works for you, and so meets the goal!

Kind regards,

Hi @Timur Khakimyanov thank you for your post. I' ve copied your solution and it works for me. 

0 votes
Jack Brickey Community Leader Jul 23, 2021

You cannot sum values across all stories. The automation math functions work within an issue. So you can sum two numeric fields within an issue. You might need to look at some add-on for this.

Hi @Andreas Safar -- Welcome to the Atlassian Community!

Yes, what Jack noted: Are you using the Server or the Cloud version?

I note you are trying to sum custom field values with Lookup Issues. 

Best regards,

Thank you for your reply. We are using the cloud version.

In other threads I saw comments where the story points or time estimates are summed up in the appropriate fields of their epic. So I was hoping to do the same just with the custom fields. Something like this:

Story 1 has value '5' in custom field

Story 2 gets a '3' entered into the custom field

Both stories are linked to the same epic

-> custom field within the epic gets updated from '5' to '8'

and so on when the custom field is set/changed/removed

Andreas you cannot sum on custom fields with Lookup Issues in an automation rule, yet...

Two possible work-arounds are:

  1. Whenever a field of interest changes in a child issue, update the parent using the Change Log.  The risk here is getting out of synch if the rule does not trigger or when multiple issues change in a short timeframe.
  2. Using a webrequest, the REST API, a search filter, and text functions, get all of the issues for the parent and then convert the webrequest response into a list...using sum to add up the results.  The impact is this rule is several seconds slower, but it will be accurate.
Like Timur Khakimyanov likes this

Hi Bill, thank you again for your support. I've voted for JRACLOUD-75018

I'll try to handle it with the proposed work-arounds.



Just for your reference in the meantime I've tried the following:

With the following rules the custom field on the parent issue is changing from NULL to 0



see the history:



I'm getting the same effect with







where the following has no impact on the epic issue


Yup... {{issues}} (note the plural) is a Server version smart value used in conjunction with that batch/scheduled trigger I noted.  It doesn't work for Cloud version.

The equivalent for Cloud version batch processing is Lookup Issues...and that feature does not support custom fields.

Please see the two work-around ideas I offered to see if one of those will work for you.  Thanks!

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events