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

[Eli Solutions Team -Eli Solutions-]

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:

• Video Tutorial Link: https://youtu.be/60sWD66l19k
• Key Formula:
  • Sum Up Sub-tasks story points: {{issue.subtasks.Story Points.sum}}

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

[SolarisJIRAadmin]

The videos are great.

Thanks for sharing!

[Chris Melville]

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]

@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]

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

[Eli Solutions Team -Eli Solutions-]

Hi @Jon Zacharias

You need to use the correct capitalization for trigger issues. 

Use with the capital "I".

{{triggerIssue}}

[Joan Mira]

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

[Aneesh N J]

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

[Joel Batac]

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

[Aneesh N J]

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]

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]

I fixed it :)

I now use this:

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

[Janany Satkunam]

I am following the exact steps outlined in this post which is the same as in this video (https://www.youtube.com/watch?v=PROcxEOMyGM) 

However, the epic story points field is not updating.  I tried manually setting it to a number and then I updated the child epic's story points field.  I noticed that the epic's story point field gets to empty.  

Can anyone see what's wrong with the below and if there are anything I need to do?

[Janany Satkunam]

Got it to work.   My issue was with using "Epic Link" since we had two of these and one wasn't the right one which was getting picked up by the rule.  I explicitly specified the field and it solved the issue.