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

Branching on JQL does not work when trigger is "Field value changed"

Sune Vester Lindhe
Contributor
January 16, 2024

Hi,

I am having problems with the following rule (the real rule is much larger, this is just a cut-down version to demonstrate the challenge):

Test rule.png

The "Lookup issues" and "Log" actions are working as expected and finds and logs one issue. But the "For: JQL" action then reports no issues found which I find strange since it is the same JQL as in the "Lookup issues"-action. If I click on "For: JQL" action and use the validate JQL feature it does return one issue.

And to make it even more strange: If I change the trigger to "Manual" instead if "Field Value Changed" it works as expected: The "Log" action writes a line to the log.

The log for the two executions is here:

Automation log.png

Any thoughts anyone?

Br, Sune

1 answer

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 16, 2024

Hello @Sune Vester Lindhe 

Is this box checked or unchecked in the For Branch?

Screenshot 2024-01-16 at 6.32.18 PM.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Upcoming Jira Service Management Events