Hey community, I'm trying to make a automation work, but I cannot get it done. Good to know, we don't have Scriptrunner (or any other "JQL enhancers"). JQL out-of-the-box doesn't seem to provide logic with linkedIssues. The use case is as follows: * We have a project where Customer Support forwards customer calls on defects. * These Cases are resolved in other projects, by linked issues (mostly Bugs, sometimes other types) * For only Bugs we have SLA's. * I'm trying to create a daily alert to Slack with a list of the Cases that have breached the SLA. * So, I want to filter out the reported cases that only have linked Bugs. The current setup is as follows: First I create a {{lookupIssues}} I've tried different things to filter down to only the issues with linked Bugs, but I cannot get it to work. If I create a branch and drill down with if-statements, it (logically) still prints all the lookupIssues. I've tried to do it with an #if-equals, but I can't seem to create the right smart value for the type of the linked issues: {{#lookupIssues}} {{#if(equals(issue.outwardIssue.fields.issue.Type, "10014"))}} reported by {{reporter.displayname}} {{/}} {{/}} Hopefully someone with a better understanding can help me with this.

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

Filter in lookupIssues for issues with linked issues with issyetype "Bug"

Eelco Haeser

Hey community,

I'm trying to make a automation work, but I cannot get it done.

Good to know, we don't have Scriptrunner (or any other "JQL enhancers"). JQL out-of-the-box doesn't seem to provide logic with linkedIssues.

The use case is as follows:

We have a project where Customer Support forwards customer calls on defects.
These Cases are resolved in other projects, by linked issues (mostly Bugs, sometimes other types)
For only Bugs we have SLA's.
I'm trying to create a daily alert to Slack with a list of the Cases that have breached the SLA.
So, I want to filter out the reported cases that only have linked Bugs.

The current setup is as follows:

First I create a {{lookupIssues}}

I've tried different things to filter down to only the issues with linked Bugs, but I cannot get it to work. If I create a branch and drill down with if-statements, it (logically) still prints all the lookupIssues.

I've tried to do it with an #if-equals, but I can't seem to create the right smart value for the type of the linked issues:

{{#lookupIssues}}
{{#if(equals(issue.outwardIssue.fields.issue.Type, "10014"))}}
<{{url}} | {{key}} - {{summary}}> reported by {{reporter.displayname}}
{{/}}
{{/}}

Hopefully someone with a better understanding can help me with this.

Accepted answers

Bill Sheboy

Hi @Eelco Haeser -- Welcome to the Atlassian Community!

From what you describe, I do not believe you need smart value, list filtering as you tried.

Instead, modify your JQL to search for issueType matching what you need and then list all of the issues found by Lookup Issues. For example:

project = yourProjectName
 AND issueType = Bug
 AND priority = High
 AND status != Done
 AND status CHANGED TO 10131 BEFORE -192h
 ORDER BY cf[10047] ASC

Please adjust as needed to match your criteria.

Kind regards,
Bill

All comments

Mohammed Aamer Khan

Hi @Eelco Haeser

Try using below with an iterator

{{#if(equals(lookupIssues.outwardIssue.fields.issue.Type, "10014"))}}

Eelco Haeser

Thanks for the try, but unfortunately the slack message is empty :-(

So, apparently the if-statements returns only falses, which I know should not be the case.

Bill Sheboy

Hi @Eelco Haeser -- Welcome to the Atlassian Community!

From what you describe, I do not believe you need smart value, list filtering as you tried.

Instead, modify your JQL to search for issueType matching what you need and then list all of the issues found by Lookup Issues. For example:

project = yourProjectName
 AND issueType = Bug
 AND priority = High
 AND status != Done
 AND status CHANGED TO 10131 BEFORE -192h
 ORDER BY cf[10047] ASC

Please adjust as needed to match your criteria.

Kind regards,
Bill

Eelco Haeser

Thanks for taking the time Bill! However, or I don't fully understand your suggestion, or I wasn't clear enough 😇

The situation is as follows:

"Customer Case" (custom issuetype) in Project A links to ("Bug","Story", "Task") in projects B,C,D etc. in a 1-n relationship.

The SLA is measured against the Customer Cases, but only for those with (at least one) related Bug.

In the daily Slack alert I want to list Customer Cases with SLA breaches (not the linked Bugs).

I need the Lookupissues to create a single list in the message, rather than have a slack message for each single issue but I can't create a LookupIssues with a single JQL that filters issues with related bugs. There's no standard JQL query available for that without plugins. 😮‍💨

Bill Sheboy

Thanks for clarifying the scenario:

GIVEN a list of Customer Case issues
AND a Customer Case issue has links to other issues
WHEN one or more of the linked issues is a Bug
THEN return the Customer Case issue's data in a list of issues

Doing this one-by-one with JQL in a rule is possible using the built-in issue linking and other fields / operators.

Doing this to produce a single list of Customer Case issues is more difficult, for a couple of reasons:

Once inside of a rule iterator, such as {{#lookupIssues}}...{{/}} only things from that scope and lower are visible.
- Your rule would need to iterate over both the lookup issues AND their linked issues for the condition tests, making the "higher scope" data for the Customer Case not visible. That is, the Customer Case key is not visible.
For smart values like issuelinks, all their details appear to not be immediately available in rules in iterators. Instead they are looked up with more calls to Jira.

A workaround is to walkover all of the lookup issues data, regardless of the link types, storing the results in a carefully constructed, created variable. And then filter on that using the text match() function with a regular expression.

If you want more details on how to try this, please let me know.

Eelco Haeser

Superthanks for the clarification and the suggestion! I'll look into that (and will probably come back later for help 😅)

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

issue-link

automation