Linking Related Incidents

Related incidents can be linked together so a cluster of connected incidents is easy to find and manage as a group. One incident acts as the primary, and the others are linked under it. This keeps the register focused on distinct incidents while preserving the relationship between them.

How Linking Works

Linking is single-layer: an incident can have other incidents linked under it, or be linked under a primary incident — but not both. You cannot link an incident under one that is already linked elsewhere, so a cluster is always exactly one level deep. The interface enforces this for you: candidates that are already a primary, or already linked under another incident, are shown but cannot be selected into an invalid arrangement.

Each linked incident remains a complete record. It keeps its own status, owner, severity, dates, and remediation tickets, and it can be opened, edited, and closed independently.

Linking from an Incident

Open an incident and find the Related Incidents section in the detail view.

• From a primary incident, use the search to add incidents underneath it, or remove a linked incident to detach it. The whole cluster is listed in one table.
• From a linked incident, the section shows its primary (highlighted) and any sibling incidents for context. These are read-only — a short note directs you to open the primary incident to manage the group. A breadcrumb at the top of the modal shows which primary the incident is linked under.

Linking in Bulk

When you select multiple incidents in the register, the multi-edit panel includes a Linked Under field. Pick a primary incident to link the whole selection under it at once. Incidents that are themselves primaries are not offered as targets, keeping the single-layer rule intact. The field shows Not linked or Linked under multiple incidents to reflect the current state of your selection.

Showing Linked Incidents in the Register

By default the register collapses linked incidents, so it lists primaries and standalone incidents without the clutter of every linked record. Toggle Show Linked Incidents to reveal linked incidents alongside their primaries. The setting is remembered with your other register filters.

How Linked Incidents Are Counted in Reports

Reporting

Period reports — including board decks and executive scoring summaries — count each cluster once, under its primary incident. Linked incidents are represented by their primary and are not tallied separately, so grouping related incidents never inflates the totals, severity breakdowns, or open counts in those reports.

Linked incidents remain fully visible everywhere you work with individual records: open them from the register (with Show Linked Incidents enabled), score and respond to them, and track their timelines independently.

This means linking is safe to use for housekeeping — clustering duplicate reports or closely-related incidents — without distorting the numbers leadership sees in a report.