Do NOT Re-Open Closed Ticket with 'Thank You' comment

Cam
Contributor
December 29, 2021

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!

7 answers

3 accepted

4 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 29, 2021

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"

Tanzeen Rahman
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 27, 2023

Hello, how do you block comments on closed issues and put a note on screen? Would appreciate your response. Thanks!

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 28, 2023

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.

1 vote
Answer accepted
Fabian Lim
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 29, 2021

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

0 votes
Answer accepted
Alan Stephenson
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 29, 2021

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.

1 vote
jshippy
Contributor
April 22, 2022

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

Tim Posselwhite December 2, 2024

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! 

Like Beth Kidgell likes this
1 vote
Cam
Contributor
January 4, 2022

Thanks all for the help - this is what I thought - Appreciate the feedback!

0 votes
Adamme Mak
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 7, 2025

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?"

jshippy
Contributor
February 10, 2025

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

0 votes
Arslan baig
Banned
October 17, 2023

Thnxks

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events