Skip to content
Tutorials Center
My learning

Topics

Lesson 4 of 39 ยท Getting Started

Your First Incident

Create, assign, work and resolve an incident in ServiceNow step by step, and learn the key incident fields: caller, category, impact, urgency, priority, state and work notes.

The incident is the most famous record in ServiceNow: something is broken or degraded and someone needs it restored. Working one incident from start to finish teaches you forms, fields, assignment and states in a single sitting. The walkthrough describes the usual out-of-the-box behavior; your instance may be customized.

Open the form

In the application navigator type incident and expand Incident, then choose Create New. You can also open the list with All (or Open) and press New. A faster way, used by developers everywhere, is to enter incident.do in the navigator filter, or use the URL pattern /incident.do?sys_id=-1 (a sys_id of -1 means "new record").

The new form shows a Number (like INC0010002) that is generated when you save, and the form is divided into a header and tabs.

The key fields

Field Meaning
Caller Who reported the problem (a reference to sys_user)
Category / Subcategory What kind of problem (Hardware, Network, Software...)
Business service, Configuration item What is affected
Channel How it came in (phone, email, self-service)
State New, In Progress, On Hold, Resolved, Closed, Canceled
Impact How many people or how much business is affected
Urgency How quickly it must be fixed
Priority Calculated from impact and urgency (read-only)
Assignment group / Assigned to Who works it
Short description One-line summary, required
Description Details
Work notes / Additional comments Internal notes versus customer-visible comments

Two things trip up beginners. First, priority is not typed; it is calculated. Second, work notes are internal, while additional comments go to the caller. Both are stored in journal fields, so each entry is kept, time-stamped and cannot be overwritten.

Impact, urgency and priority

By default, priority comes from a lookup (a data lookup rule) that takes impact and urgency, each 1 (High), 2 (Medium) or 3 (Low):

Urgency 1 Urgency 2 Urgency 3
Impact 1 1 - Critical 2 - High 3 - Moderate
Impact 2 2 - High 3 - Moderate 4 - Low
Impact 3 3 - Moderate 4 - Low 5 - Planning
Python The priority matrix (stand-in)

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

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Work the incident

  1. Fill in Caller, Short description and set Impact and Urgency.
  2. Choose an Assignment group (for example Service Desk). The Assigned to list narrows to members of that group.
  3. Right-click the form header and choose Save (stay on the form) or press Submit to save and return to the list.
  4. In Work notes, write what you tried and press Post.
  5. Change State to In Progress when someone starts working.
  6. To finish, set State to Resolved. The form then requires Resolution code and Resolution notes (they show on a Resolution Information tab) because a UI policy or business rule makes them mandatory.
  7. After the configured waiting period the incident can move to Closed.

Press Ctrl+S (or Cmd+S) to save while typing, and use the form's Activity stream to read the history of work notes and field changes in order.

The incident lifecycle

flowchart LR
  A["New"] --> B["In Progress"]
  B --> C["On Hold"]
  C --> B
  B --> D["Resolved"]
  D --> E["Closed"]
  D --> B

Typical incident states; your organization can add or rename states.

Find your incident again

Open Incident > All (or Open) and use the filter. Click a column heading to sort, right-click a heading for Group By, or click the Number link to reopen the record. Later lessons (lists and encoded queries) show how to build precise filters.

Python Simulate working an incident (stand-in)

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

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Common mistakes

  • Typing a vague short description such as "Help". Others search by it; make it specific.
  • Putting private troubleshooting in Additional comments so the caller sees it.
  • Forgetting to set the assignment group, which leaves the incident invisible in the right queue.
  • Resolving without notes, which makes the knowledge base poorer.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. How is Priority normally set on an incident?

    Out of the box a lookup computes priority from impact and urgency, and the field is read-only.
  2. 2. Which field is internal-only?

    Work notes are for the team; additional comments are visible to the caller.
  3. 3. What is sys_id=-1 in a form URL?

    Using -1 as the sys_id opens a blank form for a new record.

Summary

  • An incident records a disruption and moves through states from New to Closed.
  • Impact and urgency produce priority; work notes are internal, comments are customer-visible.
  • Resolution needs a code and notes by default.
  • You can open a new form with incident.do or sys_id=-1.

Next: The Next Experience UI