Should I handle different SLAs for different customers with one SLA and different sets of goals or different SLAs?

Concretely, I want to have the following:

  • A "time to resolve" SLA that sets different goals for different priority issues. Higher priorities correspond to faster time to resolution. Priorities are Showstopper, High, Medium, Low.
  • Goals for special customers where the time is accelerated. For example, normal time to resolve for a medium priority issue is 10 days, but for a special customer it is 5 days.

It looks as if I could do this in one SLA with 8 goals (2 for each priority). Or I could do it in two SLAs with 4 goals each.

What are the pros and cons of the different approaches? Any practical experience?

-David

1 answer

Hi David,

do you already have some experience in this topic? Which way did you chose and why?

best regards

No, we haven't moved on with a JSD deployment. First, the problem with the license model (solved now by Atlassian). Meantime, the target group lost interest....

Oh, okay. But thank you for the fast response!

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Feb 15, 2018 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 ...

1,143 views 6 19
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