Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

lookupIssues returning empty and my JQL query is correct

Zak August 21, 2023

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

1 answer

1 accepted

3 votes
Answer accepted
Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 21, 2023 edited

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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 21, 2023

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 August 22, 2023

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

Like 3 people like this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
atlassian, atlassian government cloud, fedramp, webinar, register for webinar, atlassian cloud webinar, fedramp moderate offering, work faster with cloud

Unlocking the future with Atlassian Government Cloud ☁️

Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.

Register Now
AUG Leaders

Upcoming Jira Events