I love the SLA capability, but it just isn't working for our organization. We don't run a 24-hour support desk, so when a request comes in after-hours, it always violates the short-term SLAs (like "Time to First Response") because we're not around to handle it right away. If issues submitted after-hours are subject to the same SLA constraints as those submitted while the desk is open, the reports are meaningless for non-24-hour desks because they hold us to an impossible standard.
Is there any way to set service hours for the SLAs and have them not count time when outside the service hours? Alternativly, something like "Time of Day" for the "Pause on" field in an SLA setting would work as well.
This is coming real soon. I cant say exactly when * but I can say I have seen this running here internally. :)
Service Desk Architect
* Q. Hey why cant you say exactly when?
A. Because despite our best intentions to ship often and on time, not every thing happens as we want and setting an expectation that somehting will be ready on day X and then missing it by 2 weeks rightly upsets people.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
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