nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I automatically close service desk issues in Jira Cloud?

Damon Schopen

Hello,

I would like to automatically close service desk issues in JIRA Cloud that meet certain criteria. There are some automated messages from our server that can be just closed. I setup automation to transition the issue to "Resolved." That is changing the status to Resolved automatically, but the issues are still showing up under "All Open" in the queue. How can I get the issue to close out so it isn't in "All Open?"

Thanks!

Accepted answers

All comments

rahuldanwade

Hi Schopen,

You can Auto close the tickets using JIRA Automation plugin to configure periodic task which accepts JQL as a filter.

https://marketplace.atlassian.com/plugins/com.atlassian.plugin.automation.jira-automation-plugin/server/overview

But unfortunately, this plugin is not available on the cloud.

https://answers.atlassian.com/questions/32506400

Rahul

unknown

First thing, check what does your automation do when it actually "Resolve" the issue, does it just change the status? Does it populate the resolution field? Second, check what the "All Open" queue display. Does it display "All Issues that are not Closed" or "All issues that do not have a Resolution"?

Damon Schopen

Thanks Rahul. So there is not a way to do this when using the cloud edition, correct?

Nick Muldoon

Hi Damon,

Here's how I achieved automation for closing an issue after timeout with JIRA Service Desk:

Create an SLA, 'Waiting on Customer'
1. All issues, 24/7, 336h
2. 336 hours, or 2 weeks, in that state before it is breeched
Create a custom automation rule, 'Close issue on timeout'
1. When: SLA Time Remaining for 'Waiting on Customer' is breeched
2. Then: Comment on the issue publicly to let the customer know, and transition to Done

Does it sound like that approach would work in your scenario?

Thanks Damon, have a great day,
Nick Muldoon
Easy Agile, creators of Easy Agile User Story Maps and Easy Agile Roadmaps for JIRA

Meg Holbrook

Fantastic solution for us cloud users, thanks!

Jenifer Kuntz

Automation for Jira is now available for Cloud! It is my most recommended add-on for cloud customers.

Jochem Klinkhamer

Hi Nicholas,

Great solution, implemented it in my support channel. Got one question though: how do you reset the timer when a customer replies?

Added some prtscrns of my settings of the created SLA and automation rule.

Thanks in advance,

Jochem

Waiting on customer.png

Nikita Mendelbaum

@Jochem Klinkhamer Once the "Stop" condition is met (customer replied) and the "Start" condition is triggered again (support responded to customer and waiting for customer again) - the SLA timer is reset.
I think that is the difference between the "Pause on" and "Stop" conditions.
Here are my SLA and Automation settings:

Screen Shot 2020-05-12 at 17.26.39.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-service-desk

jira-service-desk-cloud