1. Introduction to Incident Management
Incident Management is one of the core processes of IT Service Management (ITSM) in ServiceNow.
Its primary objective is to restore normal IT services as quickly as possible while minimizing business disruption.
An incident is an unplanned interruption to an IT service or a reduction in the quality of an IT service.
Examples include:
- An employee cannot log in to their laptop.
- A company application is unavailable.
- An employee cannot access their email.
- A network connection is not working.
- A printer is not responding.
ServiceNow provides a centralized Incident Management process that allows IT support teams to register, prioritize, assign, track, and resolve incidents.
2. Understanding the Incident Lifecycle
An incident moves through different stages from creation to closure.
Common incident states
| State | Description |
| New | Incident has been created. |
| In Progress | Support team is investigating the issue. |
| On Hold | Incident is temporarily waiting for something. |
| Resolved | Issue has been fixed and a resolution has been recorded. |
| Closed | Incident has completed the closure process. |
| Canceled | Incident is no longer required. |
The exact available states and transitions can depend on the ServiceNow configuration.
Incident lifecycle
- User reports an issue.
- Service desk creates an incident.
- Incident is categorized and prioritized.
- Incident is assigned to a support group.
- Support team investigates the issue.
- Issue is resolved.
- User confirms or the configured closure process completes.
- Incident is closed.
3. Understanding the Incident Table
ServiceNow stores incident records in the incident table.
The incident table extends the Task table (task).
Some important fields include:
| Field | Purpose |
| Number | Unique incident number, such as INC0010001. |
| Caller | Employee reporting the issue. |
| Short Description | Brief summary of the issue. |
| Description | Detailed explanation of the issue. |
| Category | General classification of the issue. |
| Subcategory | More specific classification. |
| Impact | Business impact of the incident. |
| Urgency | How quickly the incident needs attention. |
| Priority | Determines the incident’s handling priority. |
| Assignment Group | Team responsible for resolving the incident. |
| Assigned To | Individual handling the incident. |
| State | Current incident status. |
| Work Notes | Internal updates for support teams. |
| Additional Comments | Updates that can be communicated to the user. |
| Resolution Notes | Explanation of how the issue was resolved. |
4. Understanding Impact, Urgency, and Priority
Priority determines how quickly an incident should be addressed.
ServiceNow generally calculates priority using Impact and Urgency through a configured priority lookup mechanism.
Impact
Impact represents the extent to which the incident affects business operations.
Typical values:
- High: Affects multiple users or critical business operations.
- Medium: Affects a department or limited group of users.
- Low: Affects an individual user or has limited business impact.
Urgency
Urgency represents how quickly the incident requires attention.
Typical values:
- High: Immediate attention is required.
- Medium: Resolution is required within a reasonable timeframe.
- Low: The issue can be handled through normal support processes.
Priority matrix
The following is an illustrative priority matrix. Actual mappings should be checked in the instance’s priority lookup configuration.
| Impact | Urgency | Example priority |
| High | High | P1 – Critical |
| High | Medium | P2 – High |
| Medium | High | P2 – High |
| Medium | Medium | P3 – Moderate |
| Low | Low | P5 – Planning |
5. Practical Implementation: Incident Management
Business requirement
An organization wants to automate its IT support process.
When an employee reports a network connectivity issue:
- An incident should be created.
- The incident should receive an appropriate priority.
- It should be assigned to the Network Support team.
- The support team should receive a notification.
- The incident should be tracked using an SLA.
- Resolution details should be recorded.
Step 1: Open Incident Management
- Log in to your ServiceNow instance.
- Open the Application Navigator.
- Search for Incidents.
- Navigate to Incident > All.
- Click New.
Step 2: Create an incident
Enter the following sample information:
| Field | Sample value |
| Caller | Select an existing employee |
| Category | Network |
| Subcategory | Network Connectivity |
| Short Description | Unable to connect to company network |
| Description | Employee cannot access internal company applications because the network connection is unavailable. |
| Impact | 2 – Medium |
| Urgency | 2 – Medium |
| Assignment Group | Network Support |
| State | New |
Click Submit.
The system generates an incident number.
Note: Select an existing user and assignment group from your instance. The sample values are illustrative.
Step 3: Configure automatic assignment
ServiceNow supports Assignment Rules to automatically assign records based on defined conditions.
Navigation:
- Open the Application Navigator.
- Search for Assignment Rules.
- Navigate to System Policy > Rules > Assignment.
- Click New.
- Configure the rule.
Example configuration:
| Field | Value |
| Name | Assign Network Incidents |
| Table | Incident |
| Active | True |
| Order | 100 |
| Condition | Category is Network |
Configure the assignment group as Network Support using the assignment fields available in the rule form.
Save the rule.
Expected result: Incidents matching the configured condition are automatically assigned to Network Support when the assignment rule runs.
Test this with a new matching incident.
Step 4: Configure an Incident SLA
An SLA (Service Level Agreement) defines the expected time for responding to or resolving an incident.
For example:
A P2 incident should be resolved within four business hours.
Navigation:
- Search for SLA Definitions.
- Open Service Level Management > SLA Definitions.
- Click New.
- Configure the following:
| Field | Example |
| Name | P2 Incident Resolution SLA |
| Type | SLA |
| Table | Incident |
| Duration | 4 Hours |
| Schedule | Appropriate business schedule |
| Start condition | Priority is 2 |
| Stop condition | State is Resolved |
| Active | True |
Save the SLA definition.
Important: Configure the appropriate start, pause, stop, and cancellation conditions. Test the SLA against the actual incident lifecycle and business schedule.
Step 5: Configure an Incident Notification
Notifications help keep users and support teams informed about incident updates.
Navigation:
- Search for Notifications.
- Navigate to System Notification > Email > Notifications.
- Click New.
- Enter the following example configuration:
| Field | Value |
| Name | Network Incident Created |
| Table | Incident |
| Active | True |
| When to send | Record inserted |
| Condition | Category is Network |
| Recipients | Assignment Group or configured support recipients |
Subject:
Network Incident Created: ${number}
Message:
Hello Team,
A new network incident has been created.
Incident Number: ${number}
Short Description: ${short_description}
Priority: ${priority}
Please review and take the necessary action.
Regards,
IT Service Desk
Save the notification.
Check the configured recipient fields and email settings before testing.
6. Business Rules in Incident Management
Business Rules allow developers to execute server-side logic when records are displayed, inserted, updated, or deleted.
For example, a Business Rule can prevent an incident from being resolved without resolution notes.
Practical example: Validate Resolution Notes
Navigation:
- Open System Definition > Business Rules.
- Click New.
- Configure:
| Field | Value |
| Name | Validate Incident Resolution Notes |
| Table | Incident |
| Advanced | True |
| When | Before |
| Insert | False |
| Update | True |
| Active | True |
Condition: State changes to Resolved.
Script:
(function executeRule(current, previous) {
if (current.state.changesTo(‘6’) &&
gs.nil(current.close_notes)) {
gs.addErrorMessage(
‘Please enter resolution notes before resolving the incident.’
);
current.setAbortAction(true);
}
})(current, previous);
Note: The example uses the commonly configured Resolved state value of 6. Verify the actual choice value in your instance before implementing it.
Expected result: The system prevents the incident from being resolved when resolution notes are empty.
7. Client Scripts and UI Policies
Client Scripts execute in the browser and help control form behavior.
UI Policies control form field visibility, mandatory status, and read-only behavior without requiring scripting for common use cases.
Example: Make Resolution Notes Mandatory
Requirement:
When an incident is moved to Resolved, Resolution Notes should become mandatory.
Navigation:
- Open System UI > UI Policies.
- Click New.
- Select Incident as the table.
- Enter the name: Make Resolution Notes Mandatory.
- Set the condition to State is Resolved.
- Set the UI Policy to Active.
- Submit.
- Open the UI Policy Actions related list.
- Add an action for Resolution Notes.
- Set Mandatory to True.
Test by changing an incident to Resolved.
8. Incident Resolution Process
Once the support team fixes the issue, the incident should be resolved with proper documentation.
Example:
| Field | Value |
| State | Resolved |
| Resolution Code | Solved (Work Around) or appropriate option |
| Resolution Notes | Network connectivity restored after correcting network configuration. |
| Close Notes | Employee confirmed access to internal applications. |
Save the record.
The incident can then move through the configured closure process.
