So I've come across a problem that hopefully you may be able to help.
I am getting complaints that SLAs are firing notifications right when an 
incident has been re-assigned to the particular group.
For a medium incident, 2 service targets are attached. One for response and one 
for resolution.
The response SLA target has two milestones. First at 50% and second at 75%
The first milestone will fire a notification to the supervisor.
The second milestone will fire a notification to the manager (manager of 
supervisor).

The problem is that if a group sits on a ticket and the response SLA is missed 
AND THEN assigns the ticket to another team, the other team's supervisor and 
manager also receive an email notification about the SLA being missed. The 
first team's supervisor and manager should get the notifications, but the 
second should not because it is not their team's fault the SLA was missed.

Here is how my Service targets are configured:
Start When: Status >= New
Stop When: Status >= In Progress
Exclude: Status = Pending

Here is how my milestones are configured:
50% milestone: Execute If: Status < In Progress
75% milestone: Execute If: Status < In Progress

Has anyone else experienced this same behavior and if so, what can be done to 
fix it. I'd like to find a more comprehensive way of configuring SLAs.
Also, the form that keeps track of the times for a particular SLM is 
SLM:Measurement, correct?

Thank you,
Marcelo Martinez

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"

Reply via email to