Hello, How to auto-close resolved requests after 2 weeks in a ServiceDesk project? Thanks.
Community moderators have prevented the ability to post new answers.
Hi Teza,
Jane from Automation here. Firstly, thanks for reaching out. This is one of our more popular use cases and is as simple as a two step rule. It will look something like this:
Essentially what this rule is doing is searching once a day for tickets that have been Resolved and not updated in the last 14 days, and transitions these to Done. You can of course tailor these statuses and the query to suit.
Hope that helps. Any questions, feel free to reach out again.
Cheers,
Jane
Thanks for the hack! But the audit log says throttled, I bulk moved all the tickets to Closed status and left just one ticket in Resolved to see if this works but it still says throttled in the audit logs even with just a single Jira request! Can you advise on whats causing this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What have you tried so far? Since you tagged ScriptRunner, have you tried Escalation service?
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Haven't tried much though to be honest with ya! Would like to know if I can achieve this through default Jira Service Desk automations.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Get the most out of Jira Service Management
Solve customer problems efficiently and deliver outstanding service experiences.
Learning Path
Adopt ITSM practices to deliver exceptional service
Become familiar with the principles and practices that drive ITSM. Then, learn how to configure and use Jira Service Management to implement them.
Atlassian Certified Associate
Jira Service Management Agent Essentials certification
Prove you know what's essential to providing efficient and resolution-focused service in Jira Service Management.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.