nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Summing up all the story points to an epic

Lynn Squire_1gpeqh

I am trying to use the article https://confluence.atlassian.com/jirakb/automation-rule-to-add-sum-up-story-points-from-all-the-stories-linked-to-an-epic-1108083641.html to sum up all story points into their epic but instead of summing it is giving me the difference between what it was and what the new value is. For example, if I had 4 story points and I change that to 5 in a story it changes the Epic story points by 1.

I am on Jira server.

Accepted answers

All comments

Fabio Racobaldo _Catworkx_

Hi @Lynn Squire ,

take a look to the following video https://www.youtube.com/watch?v=PROcxEOMyGM

Sum Up Story points from Stories to Epics:

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}}

Hope this helps,

Fabio

Lynn Squire_1gpeqh

The lookup issues function isn't available on Jira server, thus my issue trying to get around that.

Bill Sheboy

Hi @Lynn Squire -- Welcome to the Atlassian Community!

For a question like this, please consider posting images of your automation rule and the audit log details, showing an execution which does not work as you expect. That may provide more context for the community to help. Thanks!

Regarding your note about Server/Data Center not having the Lookup Issues action (like Cloud), the equivalent for server is the bulk-handling option for scheduled triggers or branches. Please look here to learn about that option: https://confluence.atlassian.com/automation/bulk-handling-of-issues-993924653.html

Kind regards,
Bill

Andrew_lbg5z8

There is a plugin which allows you to view this data in Epic view https://marketplace.atlassian.com/apps/1231982/epic-insights-issue-view-for-jira?tab=overview&hosting=cloud

Fabio Paglianti

Dear @Fabio Racobaldo _Catworkx_

I am trying to apply your solution but it doesn't work properly as expected.

In my scenario I have

1 Epic
n Story (or Task)
n sub-task in each story

my team adds story points in sub-task(s) level.

At the moment, I have an existing rule that add in the parent story/task the appropriate value from the sub-issues included.

Adding your rule - to add the total in the parent Epic from all the children included, it doesn't work.

It works only if I edit the story points value in the story manually but not if the value is changed by existing rule.

any suggestion?

regards

Sheik Mubarak_0mnkn9

Hi @Bill Sheboy

I am trying to create an automation rue to get the sum of story points for all the stories linked to an epic, however I am not able to find the lookup issues function. We are using Jira Server Version 9.4.14. (pasted a picture below on where I got stuck). Could you please let me know what are the other ways that I can find the total number of story points we burnt for an epic?

Bill Sheboy

Hi @Sheik Mubarak

First thing: as this is an older thread, I usually recommend creating a new question and adding a link to the old thread. That will ensure more people see your question to offer suggestions.

Back to your question...

For your version of automation rules, there are two possible ways, depending upon what you want to do with the value:

When you only need to report on a sum, such as with an email or message, use the bulk-handling feature of branches and scheduled triggers: https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html
However you appear to want to edit the parent issue, and so need a sum that can be set from inside of an existing branch. For that scenario, you may use the Send Web Request action to call a REST API function to search for the issues with the same JQL you would have used for the lookup. To learn about that approach, please look here:
- https://community.atlassian.com/t5/Jira-Software-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828
- https://confluence.atlassian.com/automation/jira-automation-actions-993924834.html#Jiraautomationactions-sendwebrequestSendoutgoingwebrequest

Kind regards,
Bill

Fabio Paglianti

dear all

I did as follows

Screenshot 2024-04-15 at 11.24.42.png

the custom rule is

{
"update":{
"Story Points" :[{
"set": {{issue.subtasks.Story Points.sum|0}}
}]
}
}

please note, we have addes four sub-issues values for internal purposes.

regards

Bill Sheboy

Hi @Fabio Paglianti

The original question is about summing for the child issues of an epic, not for summing the subtask's values. Please see the other responses for answers to that need.

And looking at your post...for updating from the subtasks' sum, the JSON edit is not needed: the smart value expression may be entered directly into the field edit from the dropdown list.

Kind regards,
Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-software

jira-software-server

atl-gruland