Skip to content

Fetch Recent incidents to check assigned to status#1980

Closed
Soumyadeep10 wants to merge 2 commits intoServiceNowDevProgram:mainfrom
Soumyadeep10:Hacktober-2025-3rd_Code_Branch
Closed

Fetch Recent incidents to check assigned to status#1980
Soumyadeep10 wants to merge 2 commits intoServiceNowDevProgram:mainfrom
Soumyadeep10:Hacktober-2025-3rd_Code_Branch

Conversation

@Soumyadeep10
Copy link
Contributor

PR Description:

This piece of code is designed to fetch 'N' number of incidents that are most rcently created along with their Assigned status.
This helps to flag potential adherence issues which might lead to customer dissatisfaction.

-What the code does:

    1. Fetches the N number of most recently created incidents and prints their 'Number', 'Created' on value and 'Assigned to' status.
    2. The incidents which are Assigned have a value of 'Assigned'.
    3. The incidents which are Unassigned have a value of '**NOT Assigned**'.

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

@ravichandra1998g ravichandra1998g self-assigned this Oct 9, 2025
Copy link
Contributor

@ravichandra1998g ravichandra1998g left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @Soumyadeep10 ,
Thank you for your contribution.

I'm going to approve this and mark as hactoberfest accepted, so that it count towards your contribution. but we cannot merge this as this is is a low effort code snippet.

you can see some of the recently merged code snippets to understand what we are aiming for..

Keep contributing!

@ravichandra1998g ravichandra1998g added the hacktoberfest-accepted The PR is accepted for Hacktoberfest, regardless of being merged or not label Oct 9, 2025
@Soumyadeep10
Copy link
Contributor Author

Hi @ravichandra1998g , Thanks a lot for that. I understand what you mean.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hacktoberfest-accepted The PR is accepted for Hacktoberfest, regardless of being merged or not

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants