How to stop sla from getting attached to incident without making changes in sla definition ?

[Diksha19]

Hi Developers,

I am looking for a solution, where I need to cancel SLA attached to child incidents. But the problem is there are more than 60 SLA definitions available in our incident process. I am trying to avoid making changes to all the existing SLA condition.

Scripts can be created to cancel the SLA but still my start condition will be met and new sla will be getting attached.

Is there a way to achieve this ? 

[Musab Rasheed]

Write a before BR on incident_sla table and check for conditions like if incident parent is not empty then do a setabort action . Mark my answer as correct or hit like

[Musab Rasheed · Accepted solution]

Hello @Diksha,

Ignore my last update as it seems it is not possible to write BR on incident_sla table, Instead please write Before BR on task_sla table with following conditions and click setabort action checkbox like below. It should work. Condition is you need to dot walk task fields , first is task.tasktype is incident and second is task.parent is not empty

This will make sure SLA doesn't get attached to Child incidents. Please mark my answer as correct or hit like based on impact

[Diksha19]

Hi Musab,

Thanks a lot, this is working and SLA is not getting created as expected.

I am just facing one more issue, I have a scenario where child tickets on getting detached from parent should take retroactive start and new sla has to be attached to the child(which is standalone now). 

As I am cancelling the earlier SLA's by default new SLA was not created

Any thoughts on this ?

[Musab Rasheed]

Hello @diksha, 

Not 100% Sure about this but as I have answer your original query Kindly mark my answer as correct so that It will help others.