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 returning empty and my JQL query is correct

Zak_gx2g9s

Hi,
I have an issue with lookupIssues, it returns empty when I trigger my rule.

Capture d'écran 2023-08-21 125705.png

As you can see I have 5 issues but when I release the version I got this message

Capture d'écran 2023-08-21 125617.png

This is what THEN contains
{{#lookupIssues}}
<{{url}}|{{key}}>: {{summary}}
{{/}}

To avoid sending an empty message, I added a condition for lookup issues size.
In addition, I added a condition to avoid sending all the previous issues that were closed on the previous releases.

I am confused because the query is working, but I am not getting the issues

Accepted answers

Mark Segall

Hi @Zak

The rule executes when the version is released which I would assume means that your 5 unreleased issues that were validated upon rule creation are no longer in an Unreleased version.

Is your intent to send release notes for the recently released version via slack? If so, you probably want to change the Lookup Issues to this:

fixVersion IN ("{{version.name}}") and status = Done

This would return all completed issues that were in the version that triggered the rule.

All comments

Mark Segall

Hi @Zak

The rule executes when the version is released which I would assume means that your 5 unreleased issues that were validated upon rule creation are no longer in an Unreleased version.

Is your intent to send release notes for the recently released version via slack? If so, you probably want to change the Lookup Issues to this:

fixVersion IN ("{{version.name}}") and status = Done

This would return all completed issues that were in the version that triggered the rule.

Bill Sheboy

Hi @Zak

Yes, and...to Mark's answer:

Looking at your rule image, it is triggered on Version Released. Yet later in the rule you perform a condition compare on {{issue.fixVersions.name}} equals {{version.name}} There are two potential problems with that comparison:

The rule is triggered on a version release, but there are no issues available for the comparison. When you want to reference the issues assigned to a version-related trigger you need a branch (or a lookup issues).
Next, will your issues *ever* have more than one fixed version assigned? If so, that {{issue.fixVersions.name}} will produce a list, and that will never match a single value from the triggering version.

Kind regards,
Bill

Zak_gx2g9s

My bad
At first, I was not using any condition, and it was working, but I did not succeed to filter tickets from the previous version.

I deleted my conditions and change the query as @Mark Segall suggested, and it seems working fine.

@Bill Sheboy No, my issues will have one version only

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