Skip to main content

Find a project's open incidents

Incidents lists every production incident across the projects you can see, resolved ones included. When you look after one project, such as at the start of an on-call shift, you want only what is still broken there. The filters above the list narrow it, and they are kept in the page's address, so you can share the view. What an incident is, and its states, is in How Production QA works.

Before you start: Incidents is part of Production QA, a plan feature. While your plan does not include it, Incidents is not in the side menu and the page shows Not on your plan.

Who can do this: anyone who can view the project.

  1. In the side menu, select Incidents. The list opens, newest first, with All projects, Any severity, Any state and Any type above it.
  2. In Project, pick the project.
  3. In State, pick Open. Each filter holds one value, so check Reopened as a second view afterwards: an incident that came back after it stopped is Reopened, not Open.
  4. To see the worst incidents, pick Critical in Severity, then switch to Error for the next level.
  5. To see only one kind of incident, pick it in Type: Monitor for your monitoring tool's alerts, Release failed, Health, Regression or Lane slowdown.
  6. Read each row: Suspect names the pull request most likely behind it, Count how many times it has happened and Seen how long ago it last did.
  7. Select a row to open the incident.
  8. To share the view, copy the page's address from your browser. Anyone who can view the project sees the same list.

The Incidents list filtered to one project and Open: two monitor incidents, each with its count, severity, state and when it was last seen

Nothing matches these filters means the project has no incident in that state; select Clear filters to see them all again. On a phone the four filters sit in one Filters menu, and its Clear turns them off. The list refreshes every 15 seconds while it is open.

Next​