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

Use automation to sum up story points for an epic but only for stories that are not rejected

Michaela Kelle-Emden

Hi,

I kow the automation to sum up the story points of all issues of an epic and write them into the story point field of the epic.

The problen is that I do not want to sum up all story points. I wont to exclude the story points of the issues that are rejected.

Do I need to add this to the "Lookup issues":

parent={{triggerIssue.parent.key|"null"}}

How?

Or do I need to extend the "Then" part:

{ "fields": { "Story Points": {{lookupIssues.Story Points.sum|0}} } }

Is it possible at all?

Regards,

Michaela

Accepted answers

Michaela Kelle-Emden

I found the solution by myself and it is so simple.

I just needed to extend the Lookup issues to:

parent={{triggerIssue.parent.key|"null"}} AND status!=Rejected

All comments

Jovin

Hey @Michaela Kelle-Emden

Should be achievable, just depends on the individual configuration you have. Can you help me with understanding the below:

How do you identify a "Rejected" issue?
Are you looking to sum the story points onto the Epic?

Michaela Kelle-Emden

I found the solution by myself and it is so simple.

I just needed to extend the Lookup issues to:

parent={{triggerIssue.parent.key|"null"}} AND status!=Rejected

Michaela Kelle-Emden

1. by the status of the issue

2. yes

Bill Sheboy

Hi @Michaela Kelle-Emden -- Welcome to the Atlassian Community!

Well done solving your own question! And...

In your original question, you asked how to "sum up the story points of all issues of an epic..." and you tried to find the child issues of the epic with this revised JQL:

parent={{triggerIssue.parent.key|"null"}} AND status!=Rejected

However if the trigger issue has no parent, that JQL will find ALL issues which do not have a parent, regardless of issue type. How are you preventing that case?

Usually a rule like this is written as:

trigger: some trigger
condition: issue type is one of Story, Task, Bug, and other types you have that could be children of an Epic
condition: parent is not empty
action: lookup issues with JQL of
- parent={{triggerIssue.parent.key}} AND status!=Rejected
...

trigger: some trigger
condition: issue type is one of Story, Task, Bug, and other types you have that could be children of an Epic
action: lookup issues
smart values condition to confirm the lookup found any issues
- first value: {{lookupIssues.size}}
- condition: does not equal
- second value: 0
...

Kind regards,
Bill

Michaela Kelle-Emden

Hi Bill,

Thank you!

Your first suggestion is acutally what I do.

Regards,

Michaela

Martin Šenkeřík _Brasscog_

Michaela's solution is exactly right - filtering by status in the JQL lookup is the cleanest approach:

parent = {{triggerIssue.parent.key|"null"}} AND status != Rejected

One thing worth adding that isn't mentioned above: lookupIssues returns at most 100 results, regardless of how many issues match the JQL. If the epic has more than ~100 non-rejected children, the sum will be silently incomplete. No error is thrown - you just get a lower number.

For most teams this cap is far enough away to not matter. But if your epics tend to be large, or if you want the rollup total to behave like a real Jira field (JQL search, board card display, dashboard gadget), a field written by an app won't have that limit.

I released TreeTotals for that - it writes rollup totals into Jira fields across the full hierarchy, without the 100-issue ceiling, without any configuration. Free up to 10 users. (Full disclosure: I'm the developer of TreeTotals.)

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-automation