Looped SLA for Customer Update

Hi I would like to set up an SLA that resets the clock once action is performed

Our users need to be updated every 4/8 hrs based on priority of the incident.

I need rule for example that once first response has been action an SLA for 8hrs starts to count down. but if I send update to customer I need the SLA to reset and begin 8hr count down again.

 

Regards

Olly

3 answers

0 votes

Hi Olly,

There is currently a feature request for this that you can find at JSDSERVER-194.  I would suggest voting on the issue and adding your use case to the comments so our devs will consider adding this functionality into JIRA.

You didn't specify Cloud or Server, however, you may want to review this post and review Rober's anwer that states you can do this with MISC Workflow Extension or Script Runner and use the Resolution field and set it on status change then use an automation rule with JQL based on resolutionDate.

Hopefully that helps.  Please don't forget to add comments and vote on JSDSERVER-194!

Cheers,

Branden

Hi we are cloud thanks for this very helpful, hopefully we can get this function one day 

0 votes
Jack Brickey Community Champion Jun 20, 2017

I don't believe resetting SLA timer is possible. You can create multiple SLAs and switch between them by associating w/ a workflow status. You may be able to toggle back in forth between the two status but unsure if timer restarts. Also, I'm wondering if something like this may work...

create a filter something like:

project = ABC and status != resolved and not updated > -4h

and set up a subscription to email every 4hours?

0 votes
Susan Hauth Community Champion Jun 20, 2017

Hi Olly,

WE have the exact scenario you are talking about.  I worked with Atlassian  and came up with a solution where it flipped between In Progress and In Progress 2 whenever there was a comment by the agent and set the SLA to start when entering these statuses.  This effectively worked but was very clunky:

1. It requires a use of 2 status to keep track on the "waiting for support" stage, and create transitions between them:

2. Create automation rules, IF comments is made by agents and the request is in Waiting for support and Request Type is not empty, THEN transition it to the Waiting for support 2 status, and vice versa (transition back from Waiting for support 2 to waiting for support)

3. Create an SLA, START when Issue created, OR entering status waiting for support, OR entering status waiting for support 2, and STOP when comment for customers

However, I found it so clunky that eventually we purchased Intenso - Extensions for Service Desk which has a reset sla post workflow function.

Hope that helps

 

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

415 views 1 13
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot