Adding Related Incidents
Related Incidents connects multiple incidents in a simple parent/child relationship for multiple use cases:
- Coordinating efforts across multiple incidents with similar root causes
- Organizing a large, complex incident into multiple smaller incidents
- Otherwise relating multiple incidents together for your own needs and criteria
You can relate incidents with a Slack command or on the Incident page on the web. To keep things simple, incidents can either be a parent or a child (but not both!), so all hierarchies are limited to one generation of parent and child(ren).
In Slack, you can relate an incident to another incident from inside either incident’s Slack channel. Run the command
/fh related and you’ll find the modal below.
You can add the appropriate related incident from that modal. Once you’ve added a related incident, you will see an announcement of the new relationship in the incident Slack channel. This announcement is posted on the thread of the pinned message in the related incidents’ Slack channels. You can add additional children from the Parent incident channel.
In the web UI, you can add related incidents from the Incident Page. Locate the “Related Incidents” section of the sidebar and click the pencil icon to edit. You’ll see a similar modal as you would in Slack, allowing you to add either a parent or multiple children to the current incident.
You can use the sidebar to quickly navigate between related incidents.
To keep private incidents secure, only private incidents can be related to other incidents marked as private. You can always convert existing incidents to private if you need to relate them to other private incidents.
Anytime that a related incident posts an update, that update will be shared on the thread of the pinned message of the other related incidents’ Slack channels. When the parent incident is pushing these notifications, they will also be posted to the children incidents’ main channel (using the “Also post to channel” option in Slack).
When resolving a parent incident, you will have an option to
- Resolve all Children - This ensures that children incidents will be included in any analytics or exports.
- Archive all Children - This ensure that children incidents will be excluded in any analytics or exports.
- Do Nothing - In cases where active work is still happening in child incidents, you may want to leave them open so that responders in those incidents can resolve or archive them when the child incident is wrapped up.
You will see these options when resolving an incident from Slack or from the web UI. When archiving a parent incident, all children incidents will also be archived.