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

Using Scriptrunner to roll up sub-tasks story points to parent issue

Liran Gabai

Hi, I know that is a hot subject among Jira, have more than 100+ threads about, suggestions with more than 3k total votes, but some reason still not solved inside Jira or some reason I don't know (the suggestion with 1.6K votes is from 2013!!!!).

As I don't like to give him im searching for the way to roll up the summing of the story points sub-tasks have into his parent issue, just to be clear about what I'm talking about is this:

Issues have sub-tasks under it; you can add story points field to sub-tasks

If you have an issue called "Story X" and under it, there are two sub-tasks with 6 story points each, then the logic is that the story will contain 12 story points, or at the minimum give the user the possibility to choose if this is how he wants to calculate story points.

So I have tried plugins and many customizations through Jira dashboard and didn't succeed, but I have found this script example under Scriptrunner documentation that rolls up time estimation to parent issue, with just simple 30 lines of listener code:

http://scriptrunner-docs.connect.adaptavist.com/jiracloud/script-listeners.html#_store_subtask_estimates_in_parent_issue_on_issue_events

So my question is if someone knows how to tweak this code (because it looks pretty simple for someone who knows how to code JQL) to roll up story points to the parent issue?

Of course, if you have other solution or clear answer (not because "this is how it works" thing that I have saw from some "coaches" out there, because good products solve user needs, and not hold him back), I would like to hear that.

Comments

Sana Safai

Hi Liran,

It should be possible to modify a few places in that script you referred.

I wrote a blog post about this about three years ago (https://riada.se/estimate-your-sub-tasks-in-jira-agile/). If you can't get it to work, feel free to reach out to me.

Liran Gabai

Hi! thank you very much, have you seen that is on the cloud? your article is on a server and not cloud, as I don't find "scripted field" under the add custom field, any idea?

Sana Safai

Ah, I missed the cloud detail; I think modifying the script that Adaptavist provided is the way to go.

Liran Gabai

Have any idea how and what to change?

I'm not sure how to do it

Sana Safai

I'd start with modifying the line that has the number 2 next to it.

.queryString("fields", "parent,timeestimate")

should get changed to

.queryString("fields", "parent,customfield_xxxxx")

where the xxxxx is the id of the story point field.

Something like that. You also need to create the "Summed Subtask Estimate" field.

This is not tested so I may be wrong here.

Liran Gabai

So the steps you suggest are:

1. Create custom field

2. create a listener in Scriptrunner with the same code

3. change the strings mentioned above, according to the custome field?

Kristian Walker _Adaptavist_

Hi Liran,

I can confirm that you can modify the Store Subtask Estimates in Parent issue on Issue events example in the documentation to sum up story points.

I have included a link here to a modified version of this example that you can use to do this.

Please note that when configuring this example as a Script Listener you will need to:

Ensure the script listener is configured to fire on the issue updated event.
Ensure lines 14 and 22 are updated to reference the ID of the Story Points field in your Jira instance.
Ensure Line 32 is set to the Story Points field as configured in the linked script above.

If this answer has solved your issue can you please accept it in order to mark this answer as correct for users who are searching for a similar issue.