I'd like a way to automate the following:
When a Service Desk Request is in 'Waiting for Customer' and has not been updated for 'n' days, the customer is notified that further information is required and if not updated in 'n' days further... ticket is closed.
Thanks for reading, looking forward to see your solutions!
Yes! We are currently doing this by manipulating SLA's. We have a couple of automation tasks that allow this to take place. The first being that any time we make a comment to the customer, it moves the ticket through the workflow into a status called "Waiting for Customer" I believe this is a canned automation script. We then have another any time the customer responds, it moves the ticket back into "Waiting for Support"
We then have an SLA created that begins counting time when a ticket enters "Waiting for Customer" status. The target for this SLA is set to 24 hours.
Lastly, we have an automation script to auto-close the tickets. The automation is built with a trigger of "if the Waiting for Customer SLA" is breached, then the action is "advance workflow to resolved" AND "make a comment of X" where X is whatever verbiage you would like to give to your end user.
Another good practice is to use the canned automation trigger where if the end user replies on the ticket, it reopens it. This will place it back into the original techs queue.
On a side note, we are going to be implementing an "Inactive" step in the workflow that issues will transition to before actually closing. This will be purely to keep up appearances with the business that we have done our due diligence to give them adequate time and communication to respond before closing the ticket.
Hi Jeff! Your idea is excellent, we are trying to do this exact same thing. I only have one problem, the SLA you've described will track the total time the issue has been on the "waiting for customer" status, not the time since the last time the issue entered that state (since there's no way to reset the SLA time right?)
For example, if the SLA target is 24hs, the issue is 18hs in "waiting for customer", then the user comments and transitions to other state. The next time the issue is "waiting for customer" the SLA would be breached after only 6hs (24-18) and not the full 24. Am I right or missing something?
Thanks in advance!
@Jeff Tillett or @Jeff Tillett How does the transition to "Waiting for Customer" restart the SLA? I have not found this to be the case by default and there are open feature requests to add that feature: https://jira.atlassian.com/browse/JSDCLOUD-194
It seems like it can be done with a few different plugins in the server version, but none that I have found for the cloud version.
I finally found the time to implement this yesterday so apologies for the delay in responding:
Here's my steps that might help you with your proposed 'INACTIVE' step also:
Screen Shot 2015-12-09 at 11.14.25.png
Automation we have implemented pt.1:
Screen Shot 2015-12-09 at 11.15.23.png
Further example of auto-transition based on breached SLA:Screen Shot 2015-12-09 at 11.15.45.pngIs this the same way you're doing it? Has anybody else got a more elegant solution?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG