The Incidents view

External channels (Slack, PagerDuty, email) are configured to interrupt the right people at the right time. The in-app Incidents view is the complete record of every change Intello has detected, including those you have intentionally chosen not to be paged about.

Where to find it

Select Incidents from the left navigation, or click the bell icon in the top bar to view the most recent items.

How it is organized

The Incidents page presents three tabs:

• Open — every incident that has not yet been resolved. This is the working queue.
• Resolved — incidents that have been closed out, retained for audit and historical reference.
• All — both states combined, useful when you are searching across history.

Each incident corresponds to a change event detected by the spec sync pipeline and can be acknowledged (claimed by a teammate without resolving it) or resolved (closed out with a note). The full triage workflow is documented in Acknowledge & resolve.

Filters

The list supports filtering by:

• Severity — limiting to Breaking when you have only a few minutes for a focused review.
• Integration — useful as a pre-deploy check on the API affected by an upcoming release.
• Assignment — restricting to incidents assigned to you.

Filter selections persist per user, so the view you open tomorrow reflects the state in which you left it.

Why the Incidents view contains more than your channels do

Alert preferences route which severities are delivered to Slack, PagerDuty, and email. The Incidents view records every change event, including safe additions that intentionally do not generate real-time alerts. It is the system of record; channels are an opinionated subset.

In practice, this means the Incidents view is where you will catch changes that warrant attention but did not justify paging — for example, a new endpoint that may be relevant to an upcoming integration.