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

Epic Story Point Sum Up (count Story Points in an Epic)

My goodness Automation has some quirks.

8 hours of head scratching later here is how to sum story points at Epic level after user update.

First, create a Custom Field.

System administration -> Issues -> Custom Field -> Number Field.

I called mine "Story Points Sum for Epic"

Second, create an automation that triggers when a 'Story Point' field is changed.

Step 1


Step 28ca436a1-4be5-41ad-b661-2fbc912fad69.png

Step 3


Step 4


Test the Automation by changing a Story Point somewhere and check log6f34f73c-81cb-40c8-a262-3f33ea9b8035.png



Hi @Paul Cooper 

Thanks for the nice step by step write up!  Two suggested improvements:

  • If you always need the epic total to be numeric, and it is possible for the stories to all have no story points, consider adding a default value to the sum: {{lookupIssues.Story Points.sum|0}}
  • This rule works for Company-managed (formerly called Classic) projects.  When doing this for Team-managed (formerly called Next-Gen), the Story Point Estimate field would be used rather than the Story Points one.

Best regards,


Thanks Bill, I will look at these suggestions and see if they improve what we are doing.

A new thing: I do need to fix the Story Points Sum for Epic field to be locked. I noticed that the field can be manually overwritten. Of course it corrects as soon as a story points in dependents update.

Paul, we have the same issue with our automation-based cycle time fields.  We address that by detecting if any of the calculated fields in the parent are edited manually, we trigger the recalc.

Hi @Paul Cooper and @Bill Sheboy ,

Did you know that JSU Automation Suite for Jira Workflows provides Calculated Fields capabilities on Jira Cloud?

By setting up a simple formula, you can have a field calculated for your Epic based on field values in the stories under your Epic (eg. sum of Story Points). Whenever the value of the field under your stories changes, the calculated field will be updated automatically. Plus, calculated fields are created as read-only fields.

I'm currently looking for Jira Cloud users to join my usability study for Calculated Fields and I'd be happy to schedule a call to get your feedback on our solution. If you would be interested, please DM me on LinkedIn.

Maria Kazakou
Product Manager at Beecom Products (an Appfire company)


Log in or Sign up to comment