change managements

[Ravi]

Requirement is to add a check on the change UI, so that when a change is pushed through to Asses, service now checks if that owing assignment group has > X number of change that have breached SLA of closure and STILL  not closed. Thus forcing the assignment group to close previous changes so that they can progress the new one. excluding ECR's

and EXPITED from the check to prevent undue service impact. 

Is this achievable if yes, kindly help with the solution/snapshots or script's. Thank you in advance. 

[Mark Manders]

This can technically be done... but you have SLA's on changes? How are they setup? Or is it an SLA starting at deployment of the change and it needs to be closed within x days?

Wouldn't it be better to just put notifications and reminders in place to change the behavior? Preventing a change to go on, because some one else didn't do his job, can be problematic. Joey needs to assess the closing of the change, but is on holiday, so Monica closes it, because otherwise her change can't go through. You want it to be done well, so just reminding them to do their job will be better than preventing them from doing their job.

You can just create a flow on the task_sla table for changes with change_request.type != emergency and on 'breach time' send a reminder, add a wait of x days, check if it's still open and send another reminder.

Or: just send out reminders every x days for all breached changes by scheduling the flow itself.

[Ravi]

Thank you Mark for answering my question promptly.