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 up Story points to epic


I have many customers that are looking to sum up Story points and other custom number fields from stories to their epics.

Waiting for this feature to be deployed:

The current status is "deployed to cloud" - is it available for use on Jira cloud? what's the chosen code for that?



9 answers

This rule works on my case and it may help you.








Sum the Story Points



Edit the Epic Story Points 


Append the comment


This works for me. Thank you. 

One question though. How to apply this to more then 1 epic?

The way Carlos has this set up is it works for any epic within the given project you're working with and keys off of as soon as a story point value has been updated that has an epic link.


Well done Carlos, thank you for figuring out this functionality. 

Like Carlos Treminio likes this

 @Carlos - Thank you for the screenshots, however i get an error when I use the syntax for Epic link. Any thoughts, please. 

@Carlos Treminio 


For me this solution unfortunately did not work, the automation even runs successfully, but even if the stories are with values ​​greater than 0, the automation is always 0 in the epic, it doesn't work.

Can you help me?


Captura de Tela 2021-11-19 às 11.38.52.pngCaptura de Tela 2021-11-19 às 11.39.03.pngCaptura de Tela 2021-11-19 às 11.39.26.png

Like Christine Lee likes this

@Andreza Santostry using "Parent" instead of "Epic Link" in the Lookup Issues component. I had the same zero sum problem, and this change worked for me.

Like # people like this

@Carlos Treminio your suggestion works a treat.  Was struggling to get this working so thank you for the assist

Hi folks - I implemented Carlos' solution and it works like a charm! Thanks Carlos! :) 

Having said that, I ran into a couple of scenarios where the Story Point totals get misaligned...

  1. If you simply remove a Story from an Epic.
  2. Or, if you change the Epic Link field on an existing Story that already has the Story Point set. Whether you're setting the Epic Link for the first time, assigning it to another Epic, or simply removing it.

In each of the above cases, the Story Point totals do not get updated on the Epic(s).  

So, to address these use cases, I created an additional Automation that gets triggered when a Story is updated. It checks to see if the Epic Link was changed, captures the changed To/From values and recalculates the Story Point totals accordingly. 

Here are the Automation settings I used...

  • Trigger: Issue Updated
  • Field Condition: Type=Story
  • Field Condition: Story Points is not empty
  • Advanced Compare Condition: If {{changelog.Epic Link}} does not equal Empty
  • Create Variable Action
    • Name: EpicLinkChangedTo
    • SmartValue: {{changelog.Epic Link.toString}}
  • Create Variable Action
    • Name: EpicLinkChangedFrom
    • SmartValue: {{changelog.Epic Link.fromString}}
  • If/Then Condition: If {{EpicLinkChangedTo}} does not equal empty
    • Branch Rule / Related issues:
      • Type: JQL
      • JQL: Key={{EpicLinkChangedTo}} 
    • Lookup Issues Action:
      • JQL: "Epic Link"={{EpicLinkChangedTo}}
    • Edit Issue Action:
      • Story Points: {{lookupIssues.Story Points.sum}}
    • Add Comment Action
      • {panel:bgColor=#e3fcef}
        *{{initiator.displayName}}* has updated the *Epic Link* on {{triggerIssue.key}} so the total Story Points on this Epic has been adjusted to *{{lookupIssues.Story Points.sum}}*.
  • If/Then Condition: If {{EpicLinkChangedFrom}} does not equal empty
    • Branch Rule / Related issues:
      • Type: JQL
      • JQL: Key={{EpicLinkChangedFrom}} 
    • Lookup Issues Action:
      • JQL: "Epic Link"={{EpicLinkChangedFrom}}
    • Edit Issue Action:
      • Story Points: {{lookupIssues.Story Points.sum}}
    • Add Comment Action
      • {panel:bgColor=#e3fcef}
        *{{initiator.displayName}}* has updated the *Epic Link* on {{triggerIssue.key}} so the total Story Points on this Epic has been adjusted to *{{lookupIssues.Story Points.sum}}*.

I hope this helps!!!  ...Cheers! :)

@Guy Anela 

Thank you very much for this detailed automation.

One question though: when I create the Branch Rule inside the "If/Then" block, it opens a new nested branch ("For JQL"). Should the following statements be inside that nested branch?


Hi @Didi Goldbart - Yes, that is correct.'ll have two separate IF blocks, one for the EpicLinkChangedTo (just as you depicted above), and another for the EpicLinkChangedFrom. Here's a screenshot of the entire Automation Rule...



Also, I ended up adding a 3rd Automation to handle the use case where a child ticket gets Deleted. Here's a screenshot of that Automation Rule as well...


I hope these help. Cheers!

Like # people like this

@Guy Anela  - This is very helpful, thank you very much (great catch adding the deleted child rule)!

I'm having some issues with the 2nd automation, its seems that an error occurred. I went over the definitions and they seems correct. Do you have any idea how do I inspect those errors? I couldn't find a log or other entry with the error details.

Hi @Didi Goldbart - Glad it was helpful.

As far as the error, you should be able to track things down by viewing the Audit log. You can expand the Show more information for the specific execution and see the Conditions that were met and the Actions that were taken...


Like Didi Goldbart likes this

Hi @Guy Anela 


Thanks a lot for this, it's awesome.

I am getting an error that I am unable to debug, although the automation is doing what it should

Screenshot 2022-07-10 at 23.14.23.png


and this is my automation, am I missing anything here? thanks a lot


Hey @Nour Durra - You're more than welcome! :)

As far as the error, which For JQL Branch is it failing in? There are two, one for the EpicLinkChangedFrom and the other for EpicLinkChangedTo. I would suggest adding some Logging Actions to log the variable values getting passed before and after it enters the loop. Like this...


Hopefully the logging will give you some clues.

@Nour Durra 

Have you found a solution to your problem. I also tried the second Automation Rule and get the same error as you.

I'm also having the same issue. It seems like the comparison of {{changelog.Epic Link}} does not equal Empty is not working as expected

I only get this error when I remove an Epic Link from a ticket

Ah figured it out. Silly mistake. When you are comparing the value of {{changelog.Epic Link}} you don't actually type "Empty" you just leave the field empty

1 vote
John McKiernan
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 26, 2020

Hi @Elad Ben-Noam ,

Thanks for your message. John from the automation team here. 

This new feature has indeed shipped last week. We are just putting a blog together right now to inform customers. 

We will also be running through this new feature in a webinar on June 11th: 

Below is the smart value you could use. However, keep in mind that at the moment it will only work for summing up subtasks to the parent rather than stories to the Epic. 

2156cf3c-f624-42ab-b451-a4fc87777e9c.pngHope that helps but any questions, just let me know.


That is great! @John McKiernan when is it planned to add support for summing up values from stories on epic level?

Like edwardotis likes this
John McKiernan
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 27, 2020

Glad it solves a problem @Sebastian Nordin !

I haven't got a date for this just yet but will make sure to update this page once that ships :) 

Like Sebastian Nordin likes this

Hi John  - Any updates on when JIRA will support summing up values from stories/tasks/sub-tasks on epic level?

Like # people like this
John McKiernan
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 14, 2020

I'm afraid not @Sameer P though if you check out the comments on this post from the engineer who built it, you might find a workaround:

@John McKiernan Can you please give a 2022 update on this feature? I tried your smart sum on a simple parent/child task relationship and it fails with the error: is not a number

@edwardotis are you looking for the feature that will sum up from stories to epics? 

Hi All - In regards to summing up Story Points for an Epic, a few teams just reported to me that the Story Points are being double counted on the Release Burndown Report now (once for the Stories and again for the summed up value on the Epic). 

Have any of you come across this? If so, how are you handling it? 

I am just implementing something like this for my client. The original automation outlined by @Carlos Treminio worked perfectly for me!

I added one additional condition though as my client wanted to exclude any issues that are in the "Done" status category. Thought I'd share in case others are interested in the same use case.

In order to achieve this I:

  1. Added the "Status" field to the automation trigger to monitor it for changes
  2. Updated the "Then: Lookup issues" JQL to be "Epic Link" = {{issue.key}} and statusCategory != Done

This will monitor the Status of issues and exclude the story points of those issues that are closed.

I followed this video and the automation kicked in but for some reason it makes the story points in the Epic 20 points regardless of how many points I put in the tasks. Any ideas?

In the Epic I get 20 points, so I went through the issues and added silly points like 88 and 23 and I get the correct number in the 'estimate' field but not in the Story Point field. 


story points 20.pngstory points 207.png

0 votes
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Apr 06, 2021 • edited

removed - posted mistakenly

Epic status by Story Points report in Jira that can also be displayed in Confluence

  • I can solve this in Jira Server edition.  But you need to have deployed Dataplane reporting plugin
  • See bottom of this link with "Alex Fairweather" reply and configuration instructions

In the meantime, you can see total number of story points on an epic by following these steps:

  1. From your board, click Backlog.
  2. Click Epics panel.
  3. Click on an epic. You will see total story points for all tickets in the selected epic that are in the same Jira project as the epic. Any ticket with a different issue key will not be included in the total. In the example (screenshot) MGRMODS-208 has 9 issues but only 4 are also MGRMODS issues and those tickets total 26 story points.

Epic total points.png

John McKiernan Can you please confirm the above is the right way to get the total story points on an epic?

I don't see this view anymore either :(

Like Christy Kudlac likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events