Hi,
I have an issue with lookupIssues, it returns empty when I trigger my rule.
As you can see I have 5 issues but when I release the version I got this message
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
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.
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:
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Earning the Mindful Member badge proves you know how to lead with kindness, plus it enters you into a giveaway for exclusive Atlassian swag. Take the quiz, grab the badge, and comment on our announcement article to spread the good vibes!
Start here
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.