Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


How to deal with short customer responses after closing a ticket?

We have a workflow in Service Desk, where the ticket goes from:
Waiting For Support
Waiting For Customer
Resolved (when we close the ticket)
Customer Reopened (if we get a customer comment after it is closed)


From "Customer Reopened" we can then transition to any of several states.

The issue we have is that very often, the Customer Reopened state is caused by a customer replying with a "Thank you", or "Great. Thanks for handling this.".

This then means that we have to Resolve the ticket again, when it wasn't really reopened. It also wastes cycles. I'm wondering if anyone knew of either a plugin or a good set of rules for deciding if a response is really asking for something else.

i.e. maybe these sets of rules:
1) Comment has more than 3 words.
2) Comment has a question mark.


1 comment

Hey Benjamin, we had the same issue and initially turned the rule off that reopens tickets on customer reply, because most customers will reply with a "Thanks" or something via email.

Later on though I played with the automation some more and came up with this solution. If a comment is added that you don't want to reopen the ticket, such as "Thanks!" or "Thank you", add a branch for that. You have to set an action for Jira to use, so I just made it call a webhook to a random url that won't do anything. That way if they reply with thanks or something nothing happens to the ticket.


If they reply with something other that your exceptions though, the second branch will catch it and reopen the ticket. Or in our case, move it from "Resolved" back to "In Progress". 


comment automation jira.png

Excellent reply, exactly what I was looking for!


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events