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

lookupissues jql not finding issues that filter jql does

Dave Furlani_2zy3uu

I'm trying to write an A4J rule to update the status on issues linked to issues in a fixVer after a release. The trigger is the released version.

My approach was to branch for each issue in the release, then use lookup issues to find the linked issues in a specific project. with the JQL failing with {{issue.key}} I tried using one of the issue keys, but still no luck. The JQL works in the filter, but not in Lookup issues (see attached images).

My dummy system layer project is DFXXSYS and my dummy UAT project is UATBUG. Bugs logged in UATBUG are linked to issues in DFXXSYS with Created/Created by.

The JQL is very simple:

issueLink = {{issue.key}} AND project = UATBUG

issueLink = DFXXSYS-79 AND project = UATBUG

Any suggestions to either make the JQL work in Lookup issues, or how to change my rule to get the outcome I'm after?

Accepted answers

Trudy P Claspill

Hello @Dave Furlani

What output are you getting in the Audit Log for the rule execution?

All comments

Trudy P Claspill

Hello @Dave Furlani

What output are you getting in the Audit Log for the rule execution?

Dave Furlani_2zy3uu

Hi @Trudy P Claspill , I get this:

Trudy P Claspill

Stepping through the Audit Log:

- According to the log there are two issues in the release and they are

DFXXSYS-80, DFXXSYS-79

- 80 doesn't match the condition that you set up inside the branch. Do you think it should have, or is that not a concern?

- 79 does match the condition, but the Lookup Issues action is returning no issues.

You've tried running the action's JQL directly in the search screen substituting in the actual issue key for 79 and that works, but validating the same explicit JQL within the rule is showing 0 issues.

I've got it! I was able to replicate your scenario.

Your JQL is looking for issues in another project. To actually be able to find the issues in the other project your rule has to have a Multiple Project Scope and name both projects as part of the scope.

When you create a single-project Scoped rule, the rule can only operate against and find issues in the single named project (with the exception of the Create and Clone Issues actions).

You need to access the rule from the Global Automations page, change it to a multiple project scope naming the DFXXSYS and UATBUG projects, and then your Lookup Issues action will work.

Note you may need to enhance your rule with additional conditions so that the it runs only against issues released from the DFXXSYS project, and so the Condition inside your branch includes checking that the issue in the release is from the DFXXSYS project.

Screen Shot 2023-08-29 at 9.28.31 AM.png

Screen Shot 2023-08-29 at 9.29.02 AM.png

Screen Shot 2023-08-29 at 9.29.11 AM.png

Dave Furlani_2zy3uu

Thanks @Trudy P Claspill

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud