Skip to content

Feature/breached incident count by group#2057

Closed
mitalizope wants to merge 3 commits intoServiceNowDevProgram:mainfrom
mitalizope:feature/breached-incident-count-by-group
Closed

Feature/breached incident count by group#2057
mitalizope wants to merge 3 commits intoServiceNowDevProgram:mainfrom
mitalizope:feature/breached-incident-count-by-group

Conversation

@mitalizope
Copy link
Contributor

@mitalizope mitalizope commented Oct 12, 2025

PR Description:

This pull request adds a new GlideAggregate API snippet.
It defines a function getBreachedIncidentCountByGroup that uses GlideAggregate on the task_sla table to calculate the total number of incidents with breached SLAs, grouped by their assignment group.
Use Case:
• Provides a backend method to retrieve SLA-breached incident counts as per assignment group.
• Useful for automation, scheduled jobs, API integrations, and custom dashboard widgets.
• Offers a performance-efficient alternative to GlideRecord loops.

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

GlideAggregate script to count the breached incidents by assignment group.
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 @mitalizope
We appreciate the effort you’ve put into this contribution. We’ve labeled it as hacktoberfest-accepted so it still counts toward your Hacktoberfest progress. Thank you for contributing!

For Hacktoberfest, we’re aiming for high-quality contributions providing real-world use developer cases.

This will not be merged as this is a standard GlideAggregate script example and there are many - examples of this use case in ServiceNow Community. You can see some of the recently merged PRs to know the kind of code snippets we are aiming for.

Expanded Snippets: Code snippets reused from the ServiceNow Documentation or API References are acceptable only if they are expanded with additional context or variations).

Please reopen/ submit a new one after adding more dynamic context/use cases that are more suitable for the open source

@ravichandra1998g ravichandra1998g added the hacktoberfest-accepted The PR is accepted for Hacktoberfest, regardless of being merged or not label Oct 12, 2025
@ravichandra1998g ravichandra1998g self-assigned this Oct 13, 2025
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