Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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 story points from all epics to parent issue



I would like to sum up the story points from all epics to their parent issue. The previous admin created a parent level (standard issue types, he called 'feature') above epic level to reflect the application structures. All applications are first divided into modules (-> feature) and then into functionalities (-> epic). 

I got the sum-up automatisation for subtasks to stories and for stories to epics but don't find anywhere how to sum-up the epics story points into the 'feature' issue type. I suppose it should be a variation on the sum-up of subtasks to stories but can't get it working.

Current formula in 'Edit issue Advanced' is (previous part is when value changes for Story Points, branch rule = 'For Parent'):

"fields": {
"customfield_10032": {{#=}}{{epics.customfield_10032.join(" + ")}}



'customfield_10032' = 'Story Points' field

'epics' in the formula is variation on 'subtasks' I use this to sum up subtasks to stories and there it works. In my case the epics are subtasks from my 'feature' level but of course this doesn't work...


Anybody who can help with this please? I would 

1 answer

1 accepted

0 votes
Answer accepted

Hi @Joost Klykens 

To do this with automation, I recommend using a JQL statement to gather the epics with the Lookup Issues action.  You may then get the sum with: {{lookupIssues.Story points.sum|0}}

Kind regards,

Hi Bill,


Thank you for the quick response. Could you give some more details please since I can't get it working and did try different variations of Lookup Issues action. Added a picture of the latest variation.


sumup epic points.jpg


Thank you very much in advance,


Hi, Joost.

You are very close to solving this!  The key here is how do you connect your features and epics: custom field, parent, link etc.?  Then write a JQL statement that selects all the siblings.

For an example patterned from your rule image and assuming use of Parent Link:

  • trigger: story points change
  • condition: issue type is epic
  • lookup issues on JQL to get the siblings: "Parent Link" = {{triggerIssue.Parent Link}}
  • branch on JQL to select the feature: key = {{triggerIssue.Parent Link}}
    • action: edit the story points in the feature to be the sum from the lookup
      • {{lookupIssues.Story points.sum|0}}

Please review/update the JQL expressions if you want to add other conditions.

Hello Bill,


Apology for the late reply due to sickness. I (of course) made it at first too difficult but got it now and it worked for the level above also! My solution in screenshot, I hope it's a good approach since I didn't use JQL before. Triggering from sub-task to feature works like a charme!

Epic to Feature SP sumup.JPG


Thank you very much,


Like Bill Sheboy likes this

Well done!  Please consider marking this question as answered to help others find solutions faster in the future.  Thanks!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Apps & Integrations

Send an Email or Publish to Confluence - What should you do with your release notes?

Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...

31 views 0 1
Read article

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