Skip to content

Conversation

@Maheshkh9738
Copy link
Contributor

PR Description:

This project automatically assigns incidents to different support groups based on the time of day. For example, incidents created during day shift are assigned to the Day Support Group, while those created during night shift go to the Night Support Group. This ensures timely handling and reduces manual routing.

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

@kmxo kmxo self-assigned this Oct 29, 2025
@kmxo
Copy link
Contributor

kmxo commented Oct 29, 2025

Hello Maheshkh9738,
To follow ServiceNow best practices, Incidents should be assigned automatically to the support group responsible for the CI or service impacted, not randomly chosen relying on the time of the day.
Please take a look at the CSDM documentation to deep dive in this matter because it is important.
Thank you for your contribution.

@kmxo kmxo closed this Oct 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants