Once our support team 'Resolves' (status) a Ticket - We then auto-'CLOSE' (status) the ticket after 3 business days.
We have another Automation Rule in place that "Re-Opens" (status) a ticket if someone comments on the ticket - in case something additional may be needed, or something was done incorrectly, etc... This has proved very helpful for the team.
However, there is ONE small annoyance - when customers simply comment "Thanks! or Thank You!" to our team closing the ticket - the rule triggers and Re-Opens the ticket. In which case our team then has to CLOSE the ticket again manually - and also re-emails the customer. Not to sound un-appreciative of considerate and kind customers!
But I am looking to see if anyone has any ideas regarding not re-Opening the tickets for these cases of certain comment types, etc./. Even a small percentage would be helpful save us time!
We have tried using conditions in our RE-OPENED automation rule (see screenshot) of checking the last comment to see if the content matches "Thank you!" or "Thanks!" as a test - but customer email signatures killed that idea.... We obviously would want to make sure we don't leave any tickets Closed that need attention - but any ideas would be appreciated!
Thanks!
Unless you can use a scripting function to parse the text of a comment and work out that it's just a thank you, there's no way to do this.
I usually block comments on closed issues and put a note on-screen to say "if you need to re-open this, please transition it"
Hello, how do you block comments on closed issues and put a note on screen? Would appreciate your response. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To block comments, see https://community.atlassian.com/t5/Jira-questions/How-do-I-remove-the-quot-comment-quot-field-from-issue-resolved/qaq-p/1026938
For the note on screen, use a "message for edit" field from the Jira Toolkit to add a field that contains the note to it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Cam
To be honest, there is not much you can do.
I'd rather have the annoying emails and close them manually, than having a critical issue not being re-opened because of an automation rule.
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I agree with what others have commented. We used to have the automation portion on our tickets but now we just close the tickets when they are done. Then, if the customer comments on the ticket we'll still get notified on the ticket but the status doesn't change.
We also get responses e-mailed to us when the customer initially responds. Sometimes it may be an annoyance but we work through those. Better than having to close a ticket that got reopened on a comment.
Note: not everyone responds, so, if we see the fix is completed and the user fails to respond after a few days we remind them again, then close the ticket as resolved. With everyone today so busy we know it is hard to always respond back on fixed issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check out this thread, we've either got this worked out, or vastly reduced the number that have to be touched.
EDIT: Better yet, this may explain things further, including the benefits AND caveats of this approach:
https://community.atlassian.com/t5/Jira-Service-Management/Using-automation-to-prevent-reopening-when-a-customer-comments/m-p/2009642#M2847
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This worked great for me! Thank you :)
Adding an automation rule with JQL for
{{comment.body}}
does not match regular expression
[Tt][HhAa][AaxXcC][Nn]?[Kk]?s? ?[Yy]?[Oo]?[Uu]?[^%]*$
sorted all my Thank you answers away and didnt re-open my tickets!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
With a little help from my AI friend, I was able to enhance the regex to be very encompassing of all the variants I see in my org. This checks for the key word text anywhere in the comment so "thank" would get caught if they said "thanks". It also doesn't matter where in the comment it's written.
(?i).*(thank|thx|thnx|thanx|appreciate|cheers|obliged|gracias|merci|danke|arigato).*
I added a second compare value for {{comment.body.length}} less than 30 so it only catches if it's a short comment. This reduces risk if a customer replies eg. "Thanks, can you also add a license for James?"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I wish I could rely on a short comment filter. However, so many of our customers reply via email, and have long signatures attached. Hopefully your experience is different, would be nice to be able to keep it limited like that :D
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.