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

[Epic Story Points] How can I make this automation rule work?

Gonzalo Perez Alonso_mpxmys

Hi,

I've recently tried to set up a rule that sums all story points to the epics on a specific project (see screenshot for more details):

(*) Note: on the Edit Issue Fields action (last step), "AVR - Epic SP (Sum)" is the name of the custom field I've created to store the sum of story points. The smart value I'm using for this one is:

After testing and checking the audit log, looks like everything is working fine but the calculated custom field is not getting any update.

Any clue?

Thanks a lot in advance.

Accepted answers

All comments

Humashankar VJ

Hi @Gonzalo Perez Alonso

Can you give a try with the below approach and see if this helps ?

Configure the trigger to "Field Value Changed" specifically for the Story Points field, ensuring the rule runs only when story points are updated.
Add conditions to check:

Issue Type is not Epic (targeting child issues).
Epic Link is not empty (ensuring association with an epic).

Use the "Lookup Issues" action with a JQL query to find all issues linked to the epic:

"Epic Link" = {{triggerIssue.epic link}}

This gathers child issues for the epic, enabling story point summation.

Configure a "Branch rule / related issues" on the Epic (parent) with an "Edit Issue Fields" action:

Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards

Marc -Devoteam-

Hi @Gonzalo Perez Alonso

Can you give the details of your edit action in the branch?

I suspect it is something like: {{lookupIssues."AVR - Epic SP (sum)".sum}}, replace this with customfield_xxxxxx

Gonzalo Perez Alonso_mpxmys

Hi @Marc -Devoteam-

Thanks for replying! Here are the details:

Already tested and still no change on the custom field:

Gonzalo Perez Alonso_mpxmys

Hi @Humashankar VJ

Thanks for replying - I already tested that solution, as I found somewhere this: Automation For Jira - How to create a rule that sums up the story points from stories to a linked epic | Automation | Atlassian Support, which is pretty similar to what you've shared.

Still not worked for me - note that I'd like to store that sum on a custom field, as my intention is hiding it after and just act as data storage for some reports.

Marc -Devoteam-

Hi @Gonzalo Perez Alonso

Are there issues related to the Epic that have not been estimated?

If so can you try the clause: {{lookupIssues.customfield_21401.sum|0}}

Gonzalo Perez Alonso_mpxmys

Yes,

Both US are linked to the epic:

After using the clause, nothing changed. Still value 0 for the custom field - the audit log keeps registering a success somehow.

Bill Sheboy

Hi @Gonzalo Perez Alonso

To isolate the problem, I recommend writing this to the audit log after the Lookup Issues action, then re-test your rule:

Story point values: {{#lookupIssues}}{{key}}:{{Story Points}}; {{/}}
Story points sum: {{lookupIssues.Story Points.sum}}

That will confirm the values are set for the issues in the lookup result.

And what is the type of the custom field where you are trying to store the result?

Kind regards,
Bill

Welcome!

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

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

jira

jira-data-center

epic

automation

data-center

story-points

jira-automation