Jira Automation: Complete Video Guides on how to Sum Up Story Points between Subtasks/Stories/Epics

Eli Solutions Team -Eli Solutions-
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
July 5, 2021

Hi Everyone,

One of the most commonly asked questions we receive here in the Jira Automation is whether or not it is possible to sum up story points between Subtasks/Stories/Epics. We are very excited to announce that we have posted 2 new video tutorials that will help you accomplish this step by step.

Sum Up Story points from Stories to Epics:

  • Video Tutorial Link:  https://youtu.be/PROcxEOMyGM 
  • Sum Up Story Points from Stories - key Formulas:
    • JQL Lookup: issuetype in (story) and "Epic Link" = "{{issue.Epic Name}}"
    • Sum Up Story Points: {{lookupIssues.Story Points.sum}}
  • Sum Up Story Points when an Epic Link is updated in a story - Key Formulas:
    • JQL Lookup: issuetype in (story) and "Epic Link" = "{{issue.Epic Name}}"
    • Sum Up Story Points: {{lookupIssues.Story Points.sum}}
  • Sum Up Story Points through a Scheduled rule - key Formulas:
    • Scheduled JQL which can be updated as you require: issuetype in (epic) and status not in (done)
    • JQL Lookup: issuetype in (story) and "Epic Link" = "{{issue.Epic Name}}"
    • Sum Up Story Points: {{lookupIssues.Story Points.sum}}

 

Sum Up Story Points from Subtasks:

 

You can use the first tutorial to update any type of relationship by modifying the conditions and JQL Lookup Issues filters. (e.g. Adding Story Points form an Epic to an Initiative)

We hope you enjoy the videos.  Please support the channel by subscribing to it.

 

Thanks,

Eli Solutions

7 comments

SolarisJIRAadmin July 6, 2021

The videos are great.

Thanks for sharing!

Like Natalia Matsyuk likes this
Chris Melville December 3, 2021

Thanks for pulling this information together.  For those of us using server/DC installation, the lookupIssues function is not supported... any suggestions on alternate methods, specifically to sum up story points into the parent Epic?

Jon Zacharias January 24, 2022

@Eli Solutions Team -Eli Solutions-  any suggestions on troubleshooting this?

I have my automation set up exactly the same way you showed in the video, and it's not working for me.

Thoughts? 

Jon Zacharias January 24, 2022

@Eli Solutions Team -Eli Solutions- to be more specific:

pic3.pngpic4.pngpic5.pngpic6.png

Eli Solutions Team -Eli Solutions-
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
January 28, 2022

Hi @Jon Zacharias

You need to use the correct capitalization for trigger issues. 

Use with the capital "I".

{{triggerIssue}}

Like # people like this
Joan Mira October 4, 2023

How can we sum up the points not only from stories, but also from tasks and bugs?

Screenshot 2023-10-04 at 11.09.03.png

Aneesh N J November 30, 2023

This option will work. The one which is showed inthe above pic

Joel Batac October 9, 2023

Is there something for Parent Link, to sum the total of Epic's Story Points?

Like Franziska Beckert likes this
Aneesh N J November 30, 2023

Do we have any option to sum up story points if the epics already linked with US updated with story points. We are adding this automation now only. Whatever user stories we creating newly or updating now the automation is working . But what about the existing linked US with story points 

machael_baksteen February 15, 2024

I got the automation working for lookupIssues.Story Points.sum for an EPIC. But I would only like the SUM for stories that are done or closed (and ignore story point for stories with an other status like ToDo). 

Anybody know how to do that?

I guess I need to add an if statement to the script below inorder too only sum up the closed and done stories

 

"fields":{
"Story points": {{lookupIssues.Story Points.sum|0}}

machael_baksteen February 15, 2024

I fixed it :)

 

I now use this:

 

parent = {{triggerIssue.parent.key}} AND ("status" = "CLOSED" OR "status" = "DONE")

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events