Issue is SLA pause condition

testingniras
Tera Contributor

I have been trying to configure a pause condition for an SLA wherein when the ticket is reassigned to another group from GROUP A, it should pause. It seems straightforward, however, I don't see it working. There are 2 conditions for it -

1.) State(state) should be one of pending/awaiting info/resolved

(or)

2.) Assignment group is not GROUP A.

For condition 1, it is setting the SLA to pause. But, when the Assignment group is changed from GROUP A to another group, it does not set the SLA to pause.

Any suggestions is welcome. Thanks!

 

7 REPLIES 7

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @testingniras 

 

Better to use OLA , instead of updating the pause condition. 

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

Hey @Dr Atul G- LNG ,

 

The SLA was configured long back, and the particular team is pretty much comfortable using them as well. I don't think they would oblige to change it to OLA. Also, as for your business use case, it should be configured as SLA.

 

Appanna M
Tera Guru

Hello @testingniras ,

Try to add one more condition along with your assignment group is not Group A and Assignment group is not empty. 

Appanna_0-1711565119397.png

 

Please Mark my Answer as Helpful, if you find this article helpful or resolves your issue.

 

Hey @Appanna M,

 

Adding another condition didn't help. SLA remains In progress state. 

 

Screenshot 2024-03-28 at 1.01.05 AM.png

Thanks for the suggestion though!