Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Advice on managing SLAs for Internal issues

Hi,

I'm seeking advice on best practice options for managing SLAs, more specifically the "Time to first response" SLA in scenarios where we need to log an internal issue where the "customer" is not external.

Probably 99% of ticket issues that come in, come in from customers where the SLA is required.  But for the 1% of ticket issues that are internal to the IT team this SLA is not relevant.  

For example we had an incident issue logged today which was assessed as Major.  This triggered our Major incident management proces and after it was resolved a Post Incident Review Issue was logged.  This is an internal issue but it still has the "Time to first response" SLA attached to it.

Open to ideas and suggestions.

Thanks,
Leigh.

1 answer

0 votes
Mirva Jousala
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Sep 22, 2023

I'm also very interested in this topic 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events