Jira automation does not match a condition for an unknown reason

[Ran Wronsky]

Hello,

I've created an automation that based on a specific selection of a custom field, sets another custom field to one of 3 options.

The trigger for that automation is the creation of the issue.

For some reason I do not understand, I'm getting the following message and the field that should update is not modified.

"

JQL condition

The following issues did not match the condition:

SLK-74407

• the issue didn't match the specified JQL (most likely)
• the chosen rule actor doesn't have permissions (or issue security level permissions) to view the issue
• the issue was deleted or wasn't indexed by Jira yet (in rare circumstances)

We recommend using the 'Issue fields condition' for more consistent results.

"

• I can't use the issue field condition in my case. My condition is a JQL with "in" operator. My JQL are running fine external to the automation.
• I don't think this is related to any permissions as the rule sometimes runs fine.
• Reading about the indexing issue, I tried adding a couple of "re-fetch" steps in the automation which did not change anything.

I'm stuck at this point. Can't figure out how to solve the problem. Any help will be greatly appreciated.

[Bill Sheboy]

Hi @Ran Wronsky 

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Kind regards,
Bill

[Jack Brickey]

Hi @Ran Wronsky ,

• what JQL is used in your rule and where (condition or trigger)
• can you share screenshots 

For the specific issue SLK-74407:

• Have you ruled out issue deleted, I.e. you can find the issue? I'm pretty sure this won't be the cause but good to rule it out.
• permissions - can you check the SLK project permissions to ensure A4J has the necessary permissions to the project to browse/edit. An interesting test would be to create a manual test rule to see if A4J could add a comment to SLK-74407.

[Ran Wronsky]

Hi,

I use one JQL to assure the filed I'm sampling is not empty.

Once it is not empty I check it's value and based on its value I set another filed to one of 3 options.

The specific SLK is not deleted. the relevant field is simply not being updated.

I have multiple other automations that add comments, copy from one project to another that are running fine with the same user.

I feel this is regarding timing issues but have no clue on how to address that.

[Jack Brickey]

Hi @Ran Wronsky , we really need to see some screenshots, and I still have the same questions I posted above.

[Ran Wronsky]

 I believe the issue is with the time it takes to run the JQL I'm using as a condition.

When I click "Validate Query" it does not get the number of issues resulting, while if I run it externally it is working.

I will need to find a way to simplify it it seems.