Overview

An incident is an unplanned interruption, or a risk of one, that needs a response. Every incident in SQIBS belongs to a service, has a priority (which sets its urgency) and moves through three statuses until it is resolved.

Opened by
The web, email, the API, or an integration
Notified by
The service's escalation policy and each person's notification rules
Ends
When it is resolved

Statuses

Status 1
Triggered
New. SQIBS notifies and escalates.
Status 2
Acknowledged
Someone is on it. Notifications stop.
Status 3
Resolved
Fixed. The incident can no longer be edited.

An acknowledged incident can be unacknowledged back to Triggered, and escalation continues. Acknowledged incidents can also be snoozed. See manage an incident.

Priority and urgency

Each incident has a priority, P1 to P5, defined by your Global Admin in Incident Priority. Priorities 1 to 3 are high urgency and 4 to 5 are low urgency. Urgency decides which of a person's notification rules apply.

Find incidents

Incidents is the first page you see after signing in. It has an incidents table (title, urgency, status, service, created, assigned to) and an activity table of recent events.

Filter the table by:

  • Status: All, Open (Triggered and Acknowledged), Triggered, Acknowledged, or Resolved.
  • Date: All, Today (from 00:00), This Week (from Sunday), This Month, or Custom Date.
  • Assigned to me: only incidents assigned to you.
  • Team: the team selector at the top of the page.

Filters combine. Click an incident title to open it.