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

Jira Automation - trigger issue not showing in JQL branch

Rees, Ian

I am creating an automation, that has a manual trigger. It looks at the fix version that the trigger issue is assigned to, then does a JQL branch based on "Fixversion= the fix version of the trigger issue

The problem I am having is that the logic in the JQL branch, never includes the trigger issue. I have cut this down to a very simple script as follows

Accepted answers

Bill Sheboy

Hi @Rees, Ian

My understanding is by default, automation rules with an issue in the trigger then remove that issue in any branching. That is, the rule engine explicitly adds this to your JQL behind the scenes. This is likely to prevent looping errors.

AND key != {{triggerIssue.key}}

One way to observe this is to intentionally add an error to dynamic JQL, and the broken JQL will show the addition in the audit log.

The workarounds for this depend upon your scenario...

If you want to count, sum, average, etc. a set of issues, use the Lookup Issues action with JQL, as that will not exclude the trigger issue
If you want to perform the same action on a group of issues, including the trigger issue, duplication is needed:
- branch to the current issue, and perform the action
- then branch to the remaining issues with JQL
Or...alter your trigger to not have an issue, such as with a scheduled trigger with no JQL

Kind regards,
Bill

All comments

Kalyan Sattaluri_iinm1n

Hello @Rees, Ian

Can you share what are you trying to do?

For ex, You could also, instead of branch, do a lookupIssues before your branch, with same JQL and do an Advanced Branch on {{lookupIssues.key}} instead and act on your result set.

Bill Sheboy

Hi @Rees, Ian

AND key != {{triggerIssue.key}}

One way to observe this is to intentionally add an error to dynamic JQL, and the broken JQL will show the addition in the audit log.

The workarounds for this depend upon your scenario...

If you want to count, sum, average, etc. a set of issues, use the Lookup Issues action with JQL, as that will not exclude the trigger issue
If you want to perform the same action on a group of issues, including the trigger issue, duplication is needed:
- branch to the current issue, and perform the action
- then branch to the remaining issues with JQL
Or...alter your trigger to not have an issue, such as with a scheduled trigger with no JQL

Kind regards,
Bill

Rees, Ian

error

Rees, Ian

Thank you for the suggestion Kalyan but I am not counting, summing or averaging issues - I am creating a new fixversion which is a clone of another fix version i.e. the issues in it are also Clones. I think the answer is to do everything in the branch and do the trigger issue separately. Thanks

Rees, Ian

Thanks for the explanation Bill - that would make sense. Now I know it is intentional logic, I am working around by doing everything in the branch and then doing the trigger issue separately. Thanks

Kalyan Sattaluri_iinm1n

Great to hear. Just FYI, you can do what you have mentioned in 1 step by Adv Branch on lookupIssues results also. Either way, many ways to do this and glad you got it sorted, Thanks!

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

automation