Incident Reassignment Tracker - Codesnippet

[Shashank102002]

PR Description:

replace this with your description

Pull Request Checklist

Overview

• Put an x inside of the square brackets to check each item.
• I have read and understood the CONTRIBUTING.md guidelines
• My pull request has a descriptive title that accurately reflects the changes and the description has been filled in above.
• I've included only files relevant to the changes described in the PR title and description
• I've created a new branch in my forked repository for this contribution

Code Quality

• My code is relevant to ServiceNow developers
• My code snippets expand meaningfully on official ServiceNow documentation (if applicable)
• I've disclosed use of ES2021 features (if applicable)
• I've tested my code snippets in a ServiceNow environment (where possible)

Repository Structure Compliance

• I've placed my code snippet(s) in one of the required top-level categories:
  • Core ServiceNow APIs/
  • Server-Side Components/
  • Client-Side Components/
  • Modern Development/
  • Integration/
  • Specialized Areas/
• I've used appropriate sub-categories within the top-level categories
• Each code snippet has its own folder with a descriptive name

Documentation

• I've included a README.md file for each code snippet
• The README.md includes:
  • Description of the code snippet functionality
  • Usage instructions or examples
  • Any prerequisites or dependencies
  • (Optional) Screenshots or diagrams if helpful

Restrictions

• My PR does not include XML exports of ServiceNow records
• My PR does not contain sensitive information (passwords, API keys, tokens)
• My PR does not include changes that fall outside the described scope

[Atul-LNG]

Hi @Shashank102002

[Atul-LNG]

Hi @Shashank102002

Thanks for your participation! , a few points to note:

Querying on sys_audit is not recommended, as it can negatively impact system performance.

Regarding the second point — are you referring to reassignment count based on group or the assignee?

Also, can’t we leverage metrics here instead?

[Shashank102002]

Hiii @Atul-LNG ,
Thanks for the feedback!!!
Answer to your questions :
I used sys_audit to quickly analyze reassignment trends in real time without setting up Metrics. It gives instant visibility into how often incidents get reassigned — useful for spotting process gaps or training needs. Metrics are better for large-scale tracking, but this snippet is meant for quick insights and the reassignment count here is based on the assigned_to field, focusing on how often an incident changes hands between individual assignees.