SLA have been working fine up until I created new queues in my service project with new request types (new project that should not be connected to our current SLA goal and normal IT support) and tried to put SLA goal on "no target", so it wouldn't mess up our current SLA + SLA reports with our normal IT support.
I have a lot of different request type in our normal IT support and then we have the new request types which should not be counted in on our SLA. But it does.
On the two pictures below I tried two different ways, but none of them works.
Time to resolution:
I tried "no target" on new request types. For our normal IT support I put it on "all remaining", a certain time goal for our normal IT support request type(16h), but it includes the "no target" request types in our SLA and our SLA reports, which makes our SLA met % (report) not met.
Time to first response:
I also tried to shift it around by giving the request type for our normal IT support an certain time goal (8h) and then giving the other request types "all remaining" and "no target"/0h. But it still mess up our SLA and reports.
My solution to not getting SLA to work properly, was to go into:
report --> edit report --> and edit the specific series -> filter by specific issues --> and then the specific request types I was using for my normal SLA.
It is now showing the same as before, even though I have the new request type/new queues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.