How do I get a story issue type to sum up the story points of all issues that are split from it?
Asked by Darby Kim:

I currently want to sum up one of my fields named "Final story points" from tasks split from the story. So basically I want the field "Final story points" in the story issue to sum all "Final story points" assigned to the tasks split from the story issue automatically.


Answers:
author: Trudy Claspill
body: Hello [@Darby Kim](/t5/user/viewprofilepage/user-id/5552921)

Welcome to the Atlassian community.

You could do that with an Automation Rule.

<https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/>

Have you worked with Automation Rules before?

Jira Administrators can create Automation Rules. Often they also grant that permission to Project Administrators.

Automation rules are triggered by events, such as Issue Create, or they can be triggered manually by a user, or they can be triggered on a Schedule. In this case there are at least two, and possibly more, events that might prompt you to want to recalculate the sum.

- When an issue is split

- When a Final story point value is changed

Also, the relationship between an issue and Splits created from it is just a generic issue link relationship of split-from/split-to. Your user could create such a relationship between two issues without actually executing the Split function. They could also remove the established link between two such issues.

So that is four events so far that might prompt you to want to recalculate the sum.

It is also possible that one issue could be split, and then one of the issues created from that split could be split again. This could create multiple levels of split issues. Does that happen in your environment? Would that have to be considered in your case - rolling up the sum through multiple levels?

comments: author: Darby Kim
body: Hi [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011)

I have worked with automation rules before but extremely minimally.

I am not working with a situation that has multiple levels of split issues. It is a pretty standard situation with a story with a few tasks split from the story. I'm not sure if I set up the field incorrectly or the automation but here is what I have for the automation right now but it is not calculating the sum on the story.

I found this automation rule in another Atlassian Community post and adjusted to my particular set up.

![Screenshot 2024-07-25 at 4.21.53?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338031i9F962E715F7A7F44/image-size/large?v=v2&px=999 "Screenshot 2024-07-25 at 4.21.53?PM.png")![Screenshot 2024-07-25 at 4.22.01?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338032i7DEB7A6A95CE9189/image-size/large?v=v2&px=999 "Screenshot 2024-07-25 at 4.22.01?PM.png")


author: Trudy Claspill
body: The rule doesn't need to be that complicated.

In my example you would replace Story Points with **Final story points**

![Screenshot 2024-07-25 at 1.59.43?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338037i31144F146E558309/image-size/large?v=v2&px=999 "Screenshot 2024-07-25 at 1.59.43?PM.png")

![Screenshot 2024-07-25 at 2.00.33?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338038iD745663C130A2336/image-size/large?v=v2&px=999 "Screenshot 2024-07-25 at 2.00.33?PM.png")


author: Darby Kim
body: I inputted exactly this replacing "Story Points" with "Final story points" but it is still not working. Could something be wrong with the "Final story points" field set up?


author: Trudy Claspill
body: Please show us the rule you created, and the details of each step.

Also please show us the details of the issue where you changed the Final story points value. Show us enough of the image to show us the Final story points field in that issue, and the Linked Issues section showing that it has the "split from" link to another issue.

Also please provide a screen image showing the Audit Log output for the execution of the rule.

What type of custom field is "Final story points"


author: Bill Sheboy
body: Hi [@Darby Kim](/t5/user/viewprofilepage/user-id/5552921) -- Welcome to the Atlassian Community!

Yes, and...to Trudy's suggestions:

Are you using a company-managed or a team-managed project? You may find that in the list of projects or at the bottom-left of the page expanding area.

Company-managed projects use the "Story points" smart value, and team-managed ones use the "Story point estimate" one. Please update your rule, as needed, to sum the correct value.

Kind regards,  
Bill


author: Darby Kim
body: Hi [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011) [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313)

The custom field "Final story points" is the type where you assign a number to the field and I am using a team-managed project.


author: Darby Kim
body: Here are the screenshots of the issues where I am tracking if the automation worked:

![Screenshot 2024-07-26 at 11.50.48?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338234i3F1B0A09166F23EF/image-size/large?v=v2&px=999 "Screenshot 2024-07-26 at 11.50.48?AM.png")![Screenshot 2024-07-26 at 11.51.09?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338235i35DF2DA8B43C8991/image-size/large?v=v2&px=999 "Screenshot 2024-07-26 at 11.51.09?AM.png")![Screenshot 2024-07-26 at 11.51.25?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338236i331669866F5F4475/image-size/large?v=v2&px=999 "Screenshot 2024-07-26 at 11.51.25?AM.png")![Screenshot 2024-07-26 at 11.51.39?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338237i510E52032E754A40/image-size/large?v=v2&px=999 "Screenshot 2024-07-26 at 11.51.39?AM.png")


author: Darby Kim
body: Here are the rule details:

![Screenshot 2024-07-26 at 11.34.33?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338238i7E0909A4F42E4F22/image-size/large?v=v2&px=999 "Screenshot 2024-07-26 at 11.34.33?AM.png")![Screenshot 2024-07-26 at 11.34.44?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338239i6BB71FD5B99215C4/image-size/large?v=v2&px=999 "Screenshot 2024-07-26 at 11.34.44?AM.png")![Screenshot 2024-07-26 at 11.34.56?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338240i05058F67729E2A23/image-size/large?v=v2&px=999 "Screenshot 2024-07-26 at 11.34.56?AM.png")![Screenshot 2024-07-26 at 11.35.07?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338241i493AAC5A93D12B74/image-size/large?v=v2&px=999 "Screenshot 2024-07-26 at 11.35.07?AM.png")![Screenshot 2024-07-26 at 11.35.28?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338242iA74A11BF8337EBAE/image-size/large?v=v2&px=999 "Screenshot 2024-07-26 at 11.35.28?AM.png")


author: Darby Kim
body: Here is the audit log:

![Screenshot 2024-07-26 at 11.36.00?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338243i2B55EE463640E932/image-size/large?v=v2&px=999 "Screenshot 2024-07-26 at 11.36.00?AM.png")![Screenshot 2024-07-26 at 11.36.24?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338244i93E883236ECD556B/image-size/large?v=v2&px=999 "Screenshot 2024-07-26 at 11.36.24?AM.png")


author: Trudy Claspill
body: Hello [@Darby Kim](/t5/user/viewprofilepage/user-id/5552921)

What is the Scope defined on the Rule Details page and if it is a single project or multiple projects then what projects have you specified as being within scope?

In this step you have a syntax error. You are missing a double quote after the right-curly-braces here.

![Screenshot 2024-07-26 at 9.44.38?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/338246iDA142EF6F9B58FD6/image-size/large?v=v2&px=999 "Screenshot 2024-07-26 at 9.44.38?AM.png")

For this rule to run, you would need to Edit the Final story points field in issues TDB-10, TDB-13, or TDB-16.

In the Audit Log you can see that there are entries that show a status of **No Actions Performed.** That means the rule was triggered but there was some condition or branch in the rule where the triggering issue didn't match the condition. You can click on the **Show more** link to the right of those entries to reveal more details. When we ask for the details of the Audit Log for the rule execution, we want those **Show more** details.

(The status CONFIG CHANGED is an entry for when you have made some change to the rule. Besides No Actions Performed, for entries that are generated by the rule getting triggered you might see statuses such as Success, or Some Errors, or Failed. Refer to this document for more information on the Audit Log.

<https://support.atlassian.com/cloud-automation/docs/what-is-the-automation-audit-log/>)

After correcting the error in the Lookup Issues action, please make a change to just one of the three issues created from the Split process. Then go to the rule's Audit Log and look for the entry for the execution of the rule and share with us the **Show more** details.


author: Darby Kim
body: [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011) Thank you!! The added quotation worked!


author: Mehmet A _Bloompeak_
body: Hi [@Darby Kim](/t5/user/viewprofilepage/user-id/5552921)

Welcome to the Atlassian Community!

If you prefer using a marketplace app, you can try [Sum Up Reports for Jira](https://marketplace.atlassian.com/1231321) app developed by our team. This app provides various table reports based on the fields you choose. For your case, you can create a report that sums up "Final story points" grouped by Parent.

++App Features:++

* You can list the issue fields you want and sum up the values at the bottom.
* You can group your data on any field (sprint, status, assignee, component, project etc.) and sum up the field values (story points, time estimate etc.) or take averages.
* You can add this app as a gadget to your Jira dashboards.

Here is our [live demo dashboard](https://sumup-pro.bloompeak.io/demo) where you can see and modify any sample report and play with it.

For further details, you can have a look at [Sum Up and Average Reports in Jira Dashboards](https://community.atlassian.com/t5/App-Central/Sum-Up-and-Average-Reports-in-Jira-Dashboards/ba-p/2596950) article.

If you have any questions, feel free to [schedule a demo](https://bloompeak.io/schedule-a-call) with us.

Hope it helps.


Tags: cloud

jira-cloud