Out-of-the-box (OOTB) Assignment Group deletion capabilities do not seem to consistently work / apply to all modules, in addition where it does apply, closed out interactions containing the Assignment Group that was deleted get overwritten with "DEFAULT" as the Assignment Group instead of retaining the original Assignment Group value (if "DEFAULT" was chosen as the replacement Assignment Group in the delete function). This was not expected.
This same behaviour does not apply to incidents containing the old Assignment Group -- only open incidents get updated with the replacement value; closed incidents retain the original Assignment Group value (this is what was expected).
Only the Service Desk and Incident Management modules' tickets seem to get updated by OOTB delete capabilities.
In light of the above constraints, we require a solution to this to address the handling of obsolete Assignment Groups and it is my understanding that this can be done via incorporation of changes to the OOTB delete capabilites, or by adding a checkbox field to the Assignment Group form to control the status and visibility of Assignment Groups -- i.e., whether they are "active" and visible or not.
Is there a recommended approach on this amongst forum users? Are there any risks to either approach (data-wise, performance-wise, etc. )?
Informed thoughts are welcome on this. Thank you in advance!