The JQL I have wrote for my service project keep giving the prompt "no action"

[Sebastian Okstoft Ferraris]

Hi

For my service project, I have mad an atomated rule, that should take all requests from one of my portal groups (i have two) and direct them to a specific email address. So that all of the request goes to a supervisor that then sorts them and forwards them afterwards. 

The issue I'm having is I do not know what to write in my JQL field so that it recognizes it automatically and then sends the email, can you guys help me ?   

Right now my JQL states this: 

"Customer Request Type" = "Common questions for ME / Ask a question"

The picture below shows the service page. 

[Walter Buggenhout · Accepted solution]

Hi @Sebastian Okstoft Ferraris and welcome to the Community!

For questions about automation rules, please share screenshots showing your full automation rule as you have it right now and - in this specific case - also of the workflow associated with the Common questions ..." request type.

What you want to do suggests your JQL and rule should look more or less like this:

Trigger: Scheduled (e.g. run the rule once per day of at specified time intervals)

• JQL:

• "Customer Request Type" = "Common questions for ME / Ask a question" AND
  assignee IS EMPTY

Action: Edit issue (set your supervisor as the assignee of the issue(s))

Hope this helps!

[Sebastian Okstoft Ferraris]

[Sebastian Okstoft Ferraris]

Hi, thank you for your response, this is how my atomated rule looks like at the moment.  And here is the workflow related to the request, does this help you further in assisting me? 

[Walter Buggenhout]

I had not looked very closely at your JQL yet, but "Customer Request Type" should be "Request Type".

If you change that, you should be fine. If you still see Invalid JQL errors, try to run your query in Filters > View all issues. You will be able to see there if it is valid.

At the same time, if you want to respond to the issue created event, it is even easier to use an issue fields condition instead of the JQL condition you're trying to apply there:

That will just allow you to select the appropriate request type from a list, so you can't possibly make any mistakes.

[Tessa Tuteleers]

I just want to add to this that indeed it is easier (and better for performance of the rule) to use an issue fields condition. 

However, in this specific case you should be mindfull of a specific bug. 

When using the issue fields condition with "Request type", the condition will fail if you have added translations in JSM for the Request type (And the request was originally created in a different language). 

Using the JQL query makes sure this does not happen. 

So unless your JSM project does not have any translations, I woud advice to keep using a JQL condition for the Request types. 

[Sebastian Okstoft Ferraris]

Hi, based on the information I have provided what would my JQL need to function, it keeps saying "no action preformed" in the audit log? 

[Sebastian Okstoft Ferraris]

This is meeasge the JQL display