Incident Reassignment Tracker - CodeSnippet

Server-Side Components/Background Scripts/Incident Reassignment Tracker/Incident Reassignment Tracker.js

@@ -0,0 +1,32 @@
+(function() {
+    var MAX_REASSIGNMENTS = 5;
+    var flaggedIncidents = [];
+    var flaggedCount = 0;
+    var totalChecked = 0;
+    var incGR = new GlideRecord('incident');
+    incGR.addActiveQuery();
+    incGR.query();
+    while (incGR.next()) {
+        totalChecked++;
+        // Count how many times 'assigned_to' changed
+        var auditAgg = new GlideAggregate('sys_audit');
+        auditAgg.addQuery('documentkey', incGR.getUniqueValue());
+        auditAgg.addQuery('fieldname', 'assigned_to');
+        auditAgg.addAggregate('COUNT');
+        auditAgg.query();
+        var reassignmentCount = 0;
+        if (auditAgg.next()) {
+            reassignmentCount = parseInt(auditAgg.getAggregate('COUNT'), 10);
+        }
+        // Flag incidents exceeding threshold
+        if (reassignmentCount > MAX_REASSIGNMENTS) {
+            flaggedIncidents.push(incGR.getValue('number'));
+            flaggedCount++;
+        }
+    }
+    gs.info(' Checked: ' + totalChecked + ' | Flagged: ' + flaggedCount + ' | Threshold: ' + MAX_REASSIGNMENTS);
+    if (flaggedIncidents.length > 0)
+        gs.info(' Flagged Incidents: ' + flaggedIncidents.join(', '));
+    else
+        gs.info(' No incidents exceeded the reassignment threshold.');
+})();

Server-Side Components/Background Scripts/Incident Reassignment Tracker/README.md

@@ -0,0 +1,9 @@
+Incident Reassignment Tracker
+Use Case - 
+In IT service management, incidents are sometimes reassigned multiple times before reaching the right technician.  
+This script helps identify incidents that have been **reassigned more than 5 times**, so managers can review the assignment process and reduce ticket bouncing.
+
+How It Works -
+1. Loops through all **active incidents**.
+2. Counts how many times the **`assigned_to`** field changed using the `sys_audit` table.
+3. Prints the incident numbers in the system logs if they exceed the threshold (5 reassignments by default).

Server-Side Components/Background Scripts/Orphaned Users/README.md

@@ -0,0 +1,4 @@
+This script identifies active users in ServiceNow who have no group memberships and no roles assigned.
+It queries the sys_user table for all active users, then checks each user against the sys_user_grmember table (groups) and the sys_user_has_role table (roles).
+If a user has no associated groups and no assigned roles, their username is added to a list called orphanedUsers.
+Finally, the script prints the list, which can be used for user cleanup, security audits, or compliance purposes to ensure proper user management.

Server-Side Components/Background Scripts/Orphaned Users/Users with no groups and roles.js

@@ -0,0 +1,23 @@
+var userRecord = new GlideRecord('sys_user');
+userRecord.addQuery('active', true);
+userRecord.query();
+
+var orphanedUsers = [];
+
+while(userRecord.next()) {
+    var userSysId = userRecord.getValue('sys_id'); 
+
+    var userGroups = new GlideRecord('sys_user_grmember');
+    userGroups.addQuery('user', userSysId); 
+    userGroups.query();
+
+    var userRoles = new GlideRecord('sys_user_has_role');
+    userRoles.addQuery('user', userSysId); 
+    userRoles.query();
+
+    if(!userGroups.hasNext() && !userRoles.hasNext()) {
+        orphanedUsers.push(userRecord.getValue('user_name')); 
+    }
+}
+
+gs.print('Orphaned Users: ' + orphanedUsers.join(', '));