Hi Shawn,
I personally haven't had the issue that an Automation didn't fire despite all criteria being filled. When you say it's not working, does it simply not trigger or is it triggered but not doing anything?
Maybe noteworthy that there were ongoing technical issues also affecting Automation rules yesterday and (parts) of today. (see https://jira-software.status.atlassian.com/ and search for Automations)
If it triggers but is not doing what it should:
You are filtering for both the Request Type and the Priority in your Else-if. Can you confirm that the created ticket has the correct priority in order to proceed in the Automation?
Apart from that, I always recommend using a "Log action" action to print out smart values during runtime of the Automation that I can check after the rule ran and confirm that they have the value that I expected them to have.
In your case you could add a "Log action" action before your Else-If statement and print {{issue.priority}} to make sure the Priority of the ticket is what you expect. However, for a simple field like Priority, you can also just check the Priority of the ticket itself - it's more valuable in situations where the values aren't easily accessible or change over the course of an Automation.
I hope this helps!
Greetings
Philipp
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.