We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
Comments
can I suggest that your SLO build in the time that it takes a vendor to resolve the job..
e.g try and match up YouR vendor SLAs to your Custer SLAs (while building in a little fat) this is the ITIL approach anyways.
ON A side note, I can see how this feature would be useful for waiting on users..
Adrian
I was told this was on Cireson's map 2 years ago and not heard anything since. We too would like the ability to pause SLAs on certain criteria e.g. Incident moves to "pending" state. We are currently achieving this using a crude workaround.
That shows a way of doing it, but as the article mentions this is not supported by Microsoft. We've looked at implementing this, but have had a lot of pushback. It's possible we will still integrate something in the future, but we've put this on hold for now.
Any chance that this is on the table again for consideration?
We've been successful using this for Incidents for many years. Now Leadership wants to implement the same thing for Service Requests. Think this should be easily adaptable?