Oct 2026: Incident Management - Link related incidents

What it is and why it matters Incident Management

Link Related Incidents is a new enhancement in Incident Management that lets users connect an incident to other incidents that relate to it.

Previously, each incident stood on its own. Where several incidents were connected, such as repeat events at the same location or a follow-up to an earlier report, there was no way to record that relationship on the incident itself. Users had to rely on memory, notes or manual searching to piece the story together.

With this update, related incidents can be linked from the incident detail page so connected events can be reviewed side by side. This makes it easier to spot patterns, understand the full context of an event and carry out more informed reviews.

As part of the same update, the incident History filter now applies the From and To dates correctly, and shows draft incidents when Draft is selected.

When to use this

This feature is useful whenever one incident has a clear connection to another. It is particularly relevant if you:

• deal with repeat incidents at the same location or involving the same people
• raise follow-up incidents that relate to an earlier report
• need to review a series of connected events as part of an investigation
• want to identify patterns and trends across your incident records

For example, if a second trespass is reported at the same entrance a week after the first,the two incidents can be linked so anyone reviewing either one can see the other straightaway.

How it works at a high level

An incident can be linked to other related incidents from its detail page.

Once linked, the connected incidents are shown together, so a reviewer can move between them without searching for each one separately.

The incident History filter can then be used to narrow down incidents by date range and status when looking for related records to link.

Best practice tips

To get the most value from this update, we recommend the following:

• Link incidents as soon as the connection is known: Adding the link while the detail is fresh keeps records accurate and saves time during later reviews.
  

• Agree what counts as related: Set a simple team rule for when incidents should be linked, such as same location, same individuals or same root cause, so linking is applied consistently.
  
  
• Use links to support investigations and reporting: Reviewing linked incidents together can reveal patterns that are easy to miss when each incident is looked at on its own.
  
  
• Keep each incident record complete: A link adds context but does not replace it. Each incident should still contain its own full details.
  
  
• Use the History filter to find candidates: Filter by date range to find earlier incidents that may be connected to a new report.