I have a client whose contracted SLA specifies one response time if an issue is created during working hours and a different (longer) time if an issue is created outside of working hours. Can this be implemented in JIRA Service Desk (cloud) and, if so, how?
What I want to implement is a rule that duplicates this logic (the part in bold is what I'm specifically asking about, but I thought seeing the full logic might help get a better answer):
If priority = 1 then ( if (created_time < 8:00 AM or created_time > 5:00 PM) target = 1h else target = 30m ) else if priority = 2 then target = 1h else if priority = 3 then target = 10h else if priority = 4 then target = 20h else target = 50h
To resolve your issue you need to define a calendar first which covers the 8am to 5pm time period. See below for example
You can also add in any holidays to this calendar that you want to ignore so this might include public holidays as well as agreed periods when the SLA is relaxed. Here is an example with the 1st of January set as a holiday.
Now that you have two different calendars we can create the SLA tracking. So here is an example showing how you would build up your condition as described above.
Note that the way SLA is calculated is each line is considered in turn until the JQL returns true and the calendar timing matches. So the first two lines cover your P1 and different times.
Using this approach you can build complex SLAs with ease. One thing to note is this will have some curious results when an issue is raised at 4:31 pm as it will originally have a 30m target, or at 7:31 where it would have a 1 hour target. You may need to consider how you want to handle these edge cases.
Hope this helps
Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...
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!
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