Skip to content
Tutorials Center
My learning

Topics

Lesson 32 of 39 ยท ITSM and Administration

Incident, Problem and Change Management in ServiceNow

Learn how ServiceNow ITSM handles incidents, problems and changes: lifecycles, priority from impact and urgency, change types and the relationship between the three.

ServiceNow began as an IT service management (ITSM) tool, and these three processes remain its core. They follow ITIL practices, the widely used framework for running IT services. The processes are different on purpose: an incident restores service, a problem removes the cause, and a change controls how fixes reach production.

ServiceNow runs on an instance, so the lesson describes fields and states and offers JavaScript stand-ins that model the calculations. The state names below are the common defaults; your instance may rename or extend them.

Incident management

An incident is an unplanned interruption or reduction in quality of a service: "email is down", "my laptop will not start". The goal is to restore service quickly, not to find the root cause.

Key fields on the Incident form: Caller, Category / Subcategory, Configuration item, Short description, Impact, Urgency, Priority, Assignment group, Assigned to, State and Work notes (internal) and Additional comments (visible to the caller).

Default states: New, In Progress, On Hold, Resolved, Closed, Canceled. Moving to Resolved requires a Resolution code and Resolution notes. Closed follows automatically after a few days, or the caller confirms.

Priority from impact and urgency

Priority is usually calculated, not typed. A data lookup rule (the Priority Data Lookup, table dl_u_priority) maps impact and urgency to priority:

Urgency 1 (High) Urgency 2 (Medium) Urgency 3 (Low)
Impact 1 (High) 1 Critical 2 High 3 Moderate
Impact 2 (Medium) 2 High 3 Moderate 4 Low
Impact 3 (Low) 3 Moderate 4 Low 5 Planning

Impact is how many people or how much business is affected. Urgency is how fast it must be fixed. A single VP's laptop may be low impact and high urgency, which gives a moderate priority, and that is the point of having two inputs.

JS Stand-in: priority lookup from impact and urgency

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Typical incident flow

flowchart LR
    N["New"] --> P["In Progress"]
    P --> H["On Hold (waiting)"]
    H --> P
    P --> R["Resolved"]
    R --> C["Closed"]
    R -->|"caller disagrees"| P

On Hold states usually pause the SLA clock and need a reason, such as Awaiting Caller.

Good practice: write a clear short description ("Cannot connect to VPN from home Wi-Fi"), record work notes as you go, and link to Knowledge articles you used.

Problem management

A problem is the underlying cause of one or more incidents. You open one when incidents repeat, or when a major incident needs a root-cause analysis. Fields include Problem statement, Cause notes, Fix notes, and the Known Error flag with a Workaround.

The life cycle: New, Assess, Root Cause Analysis, Fix in Progress, Resolved, Closed. Incidents link to the problem with the Problem reference field, and resolving the problem can resolve the related incidents. A known error is a problem with a documented cause and workaround, so service desk staff can resolve new incidents quickly using the workaround field.

Remember the split: incident management is about speed, problem management about prevention.

Change management

A change request controls a modification to production: a software release, a firewall rule, a server reboot. The goal is to reduce risk while enabling change.

Change types:

Type Meaning Approval
Standard Pre-approved, low risk, repeatable (from a template or catalog) None per use
Normal Needs assessment and authorization Approval by managers and CAB
Emergency Urgent fix, rapid process Expedited approvals

A normal change moves through states such as New, Assess, Authorize, Scheduled, Implement, Review and Closed. During Assess, the risk and impact are calculated from answers or conditions (the Risk Assessment and Change Risk Calculation records). In Authorize, approvers decide. The CAB (change advisory board) can be consulted for higher risk. Conflict detection warns if another change affects the same configuration item in the same window.

Useful related records: Change Tasks (work items), Blackout windows (dates when changes are not allowed) and Maintenance windows.

Risk calculation

JS Stand-in: score change risk from answers

Press Run (or Ctrl + Enter) to see the console output here.

No output.

How the three connect

  • Many similar incidents suggest a problem.
  • A problem's fix is usually delivered as a change.
  • A change that goes wrong causes incidents.
  • All three can point at a Configuration Item (CI) in the CMDB, which helps with impact analysis and trend reports.

A good practice is to use Task inheritance: Incident, Problem and Change are child tables of Task, so they share fields such as Number, State, Assignment group, SLA records and Activity stream. Triggers on the Task table can target them all, so condition carefully.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the main goal of incident management?

    Incident management restores service; problem management looks for the cause.
  2. 2. In the default priority lookup, impact 1 and urgency 1 give which priority?

    High impact with high urgency maps to priority 1.
  3. 3. Which change type is pre-approved and used for repeatable low-risk work?

    Standard changes follow an approved template and do not need individual approval.
  4. 4. What does a Known Error record let the service desk do?

    A known error has a documented cause and workaround that agents can apply to related incidents.

Summary

  • Incidents restore service, problems remove causes, changes control modifications.
  • Priority comes from impact and urgency via a data lookup; states drive SLAs and notifications.
  • Change types are Standard, Normal and Emergency, with risk assessment, approvals and conflict detection.
  • All three are Task children and can reference CIs.

Next: Service Catalog and Request Fulfillment