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

Next challenges

Recent achievements

Recognition

  • Give kudos
  • My kudos

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

SLA for 1 organization with different calendars Edited

Hello.

Please assist to set up SLA for resolution and time to first response in the following case: 

There are 2 different conditions from the client site:

Time to response/resolution in peak time  (Monday-Sunday inclusive 14-19 GMT-4)

Time to response/resolution off peak time

 I created 2 calendars Peak Time (includes only peak time hours) and Off Peak Time, but SLA is counted incorrectly. 

Please help to change the calendars correctly using the example:

Time to resolution for critical issue in peak time is 2h 30 minutes, time to resolution for critical issue off peak time is 3h.

Also please clarify wether it's possible to set SLA for updates. For example, for critical issue the first response has been provided in 30 minutes and the ticket should be updated each 30 minutes by our team.

 

1 answer

0 votes

Hi,

Would it be possible for you to paste a picture of how your SLA is set up with your different calendars.  I'm not sure if it's entirely possible for you to do what you are trying to accomplish.

In your goals part of the SLA I think you would have to try and write something into the JQL like Created >=Startofday(+9h) and created <= Startofday(+18h) and attach that to your peak calendar.  And then the other times of the day would go to your non-peak calendar.

As far as SLA for updates we do that by using Extension for Jira Service Desk, the post workflow function: Reset SLA.  We use an SLA timer that counts down every 1 hour for critical issue.  When we publicly comment back to the customer, we use an automation to trigger the workflow function to "reset sla". 

Otherwise the only way to do that is to flip between statuses. So when you comment to your customer, add in automation that transitions the issue to a new status.  That status will then "start" your SLA again.  It's pretty tricky, that's why we use Extension for Jira Service Desk.

Hope this helps

Susan

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Asked in Jira Service Desk

Calling all Insight users, we need your help!

Hello Insight users,  As part of our (Mindville's) acquisition by Atlassian, our training team is looking to build some new Insight training materials. It would really helpful if you can ...

231 views 3 5
View question

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you