• Community
  • Products
  • Jira
  • Questions
  • I want to vary SLAs according to a) customer AND b) the product to which the incident relates. In essence, there are two levels of definition - can JIRA Service Desk cater for this?

I want to vary SLAs according to a) customer AND b) the product to which the incident relates. In essence, there are two levels of definition - can JIRA Service Desk cater for this?

This is the situation:

  1. Our customers are set up as Service Desk projects.
  2. Each customer takes different products from us.
  3. The SLA varies depending on the customer and the product. Two customers might take the same product, but their respective SLAs (i.e. timings) might well be different.

Can the SLA functionality in JIRA Service Desk deal with this? If so, how does one set this up?

Thank you! 

 

2 answers

If clients are set up in different projects, I will assume you identify which product is concerned using Components.

Your SLA for the Client 1 desk could look like this:

Time to first response:

component = product 1       8h

component = product 2       4h

 

For Client 2's desk

Time to first response:

component = product 1       6h

component = product 2       6h

https://confluence.atlassian.com/servicedeskserver031/setting-up-slas-802164805.html#SettingupSLAs-SettingupSLAgoals

Hi there,

Many thanks for your help.

If I identified the product via another custom field, for instance a dropdown, would I still be able to define the SLA around that?

 

Thank you

Of course. Any field will do. Instead of component = product 1, you would have customField = product 1. The same logic applies.

you can create your SLA's based on JQL similar to quick filters.    Each project or service desk can have its own SLAs.   you can also have multiple types of SLAs. 

 

for example, we use the Following 

Time to First Response (our Triage process) 

Time to Assign (when the ticket gets picked up

Time to Resolution (when it is done) 

 

each service desk project can have multiple SLA values. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,725 views 17 21
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