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

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Issue with automation rule not finding matching issue

We are setting up a rule when, for specific project (HD) and (via JQL) issuetype, 4 additional issues are created, copying the summary and description and linking to the original (trigger) issue. But it fails with these details:

Action details:
JQL condition
The following issues did not match the condition: HD-318 This may be due to any of the following reasons:

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 modified the Actor from automation to an actual user and the error is still happening. What is not correct?

Onboarding Automation.jpghd-323.jpgDid not match.jpg

1 answer

0 votes
Brant Schroeder Community Leader Feb 13, 2021

@Paula Manildi 

Just from what you shared it looks like the issuetype is Change and the Request Type (Customer Request Type)  is Employee onboarding.   So I believe you are correct that your JQL needs to be updated.

Hovering over the issue type only displays the issue type and then what you could do, i.e. change it. The issuetype is "Employee onboarding". jql.jpg

Brant Schroeder Community Leader Feb 13, 2021


  Great, thanks for confirming.  Can you use advanced condition compare with the following and as the trigger and see if that works for you.


I have changed the rule to use Advanced compare condition and will see if it works. 


I have changed to select Issue Type equals directly, which is what functioning rules use.


Still waiting for use cases to test.

Brant Schroeder Community Leader Feb 17, 2021

Did this fix the issue?

Like Paula Manildi likes this

Using ' select Issue Type equals ' solved the issue. Which I should have done at first, since that is what I had done in the first rule I had created. 

It is a little frustrating that 3 ways are presented to do something but only one of them work!


We are experiencing the same issue when using the JQL. Currently, we use JQL only when we need request-channel-type as a condition or when we have OR for multiple different fields.

Is there a solution or a workaround to this problem because the automation used to work perfectly.

Best wishes,
Nikolay Petrov

Like Dana Gould likes this

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Posted in Trello

Taco Tuesday: Your favorite Trello blog takeaway

Hello friends! From the community that brought you Welcome Wednesday, Throwback Thursday and Friday Fun, welcome to Taco Tuesday, a weekly discussion about all things Trello. The best part? One Tac...

60 views 4 3
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you