I have created automation. If a customer comments as "Cancel" in the comments, that will move the ticket status to Cancel. However, the rule is working fine but failing in a negative scenario. Even if a customer types something else then, also the automation fires and updates the ticket status to Cancel.
Hello @Shikha Verma
You need to remove the curly braces around Cancel in that comparison. The curly braces tell the Automation rule that is a smart value. If you want to see if the comment body contains the literal text Cancel then remove the curly braces.
Hello Trudy, thanks for the response. The solution which you have provided worked for me.
One additional question: what if we need to check both the lower and upper case for the Cancel? Right now, it's not working if a customer types in cancel instead of Cancel. I tried adding by putting (Cancel, cancel) and (Cancel | cancel) but it didn't work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think this post might help you solve your problem.
Or you could try using the contains regular expression comparison
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, Trudy, for the help! It’s working fine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Shikha Verma
For the benefit of other users that may find this post, can you show the solution you implemented?
Also, please consider marking the Answer thread as Accepted to help other users find posts with working solutions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Show up and give back by attending an Atlassian Community Event: we’ll donate $10 for every event attendee in March!
Join an Atlassian Community Event!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.