SLA on assignment group changes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2018 04:51 AM
The requirement is to have SLA created whenever the assignment group changes on the incident. The previous should get closed and the new one should be created.
Implementation:
I created a flag on the incident form named Assignment Group Changes (Boolean) with true as the default value.
I then created a simple business rule where Assignment Group Changes will change to TRUE during ticket creation/ assignment group updated.
I also put a business rule on the task_sla table which would query the incident record and would update the flag to false after a task sla is inserted (which would allow the flag on the incident form to continue to 'change').
Advanced:
(function executeRule(current, previous /*null when async*/) {
// Add your code here
var task_id = current.task;
var gr = new GlideRecord("incident");
gr.get(task_id);
gr.u_assignment_group_changes = 'false';
gr.update();
})(current, previous);
On my SLA Definition, I added in the restart condition, i have the below configured.
Issue:
1) I can see the "Assignment group changes" mark as true on the new ticket. However, it is gone after save.
2) After ticket reassigned to another assignment group, the "Assignment group changes" mark as true again but no SLA started.
What might go wrong with my implementation?
Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2018 05:45 AM
Hi,
It is all about everything happening in one transaction/thread. What I mean by that is, setting the field Assignment group changes to True and running another BS rule to make it false happens at the same transaction.
Something to remember about SLAs is, the start condition needs to be always true until the time it matches the Stop/Cancel condition otherwise, the SLA gets canceled automatically.
In your case, the start condition is met(flag=true) but again not met at the same time(flag=flase set by the BS rule). This makes the SLA never start.
Now the suggestion,
1. SLAs are good to be used for Choice fields(like priority or state) where there are a fixed set of values which can be selected. When there is no definite value which a user can select(like String or reference fields) and we just want to log the time for each value, I would recommend going for Metrics instead of SLA.
2. The second one which I would try is using event triggers and script actions.
Good Luck!
Mark it as Correct and Helpful if it was.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2020 01:22 PM
Hi Sagar and tscot,
We are having a similar issue with reporting Task_SLA table.
in particular that the SLA restarts every time a case changes its case owner/assignment group, however, the report table only show us the most currently assigned case owner/assignment group (see below a screenshot). It makes it look like the last agent or group who worked on the case caused a breach in the SLA, but it actually was one of the previously assigned agent/groups who did that.
Sagar - you mentioned Metrics/Triggers/Script Actions. Can you be more specific, in terms of suggesting which metrics/triggers would be useful to explore?
Thank you!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2020 10:24 AM
Kate,
Fundamentally, SLA is defined for a better service delivery and if the issue/request/task is completed by the desired time or not. It is not the best way for evaluating the efficiency of individuals/ITIL users.
Let me explain a bit better. SLA for a task is made keeping customer in the eyes. If the assignment is changing, why should the customer suffer? For customer, the service must be provided in the same time frame as promised. I feel the SLA should not reset in the case of reassignment. Reassignments are fulfillers responsibilities.
SLAs should get restarted only when a priority or urgency or something of that kind is updated.
Regards,
Sagar
www.zetechno.com

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2021 02:33 AM
Hello,
Why not use SLAs Breakdown?
https://docs.servicenow.com/bundle/rome-it-service-management/page/product/service-level-management/...