Skip to main content
Use an incident tracker when many requesters report the same problem, such as an outage. You link each affected ticket to one tracker ticket and work the incident there. Status and priority changes on the tracker flow to every open linked ticket. You can also broadcast a public reply to every linked requester at once.

Incidents vs merging

Incidents and merging both pull related tickets together, but they solve different problems.Use parent and child tickets instead when you break one piece of work into separate tasks that each follow their own lifecycle.

Incident trackers and ticket types

An incident tracker is a ticket that other tickets link to. Being a tracker is separate from a ticket’s : the Type property stays an editable field on the tracker and on each linked ticket, so a tracker can have any type. A ticket becomes a tracker when you create it with Create incident, or the first time a ticket is linked to it.

Create an incident

Create a tracker from one ticket or from several tickets in the web app.

From a ticket

1

Open the actions menu

On a ticket’s detail page or in a ticket list, open the ticket’s actions menu and select Create incident.
2

Fill in the tracker

The create modal opens in incident mode with the ticket listed under Related tickets. Give the tracker a title and fill in the standard ticket fields. Trackers use no ticket form, so the form picker is turned off.
3

Add more tickets

Click Add ticket under Related tickets to search for other affected tickets.
4

Create the incident

Click Create incident. Ravenna creates a new tracker ticket in the current workspace and links the selected tickets to it.
Select multiple tickets in a ticket list and choose Create Incident from the bulk actions menu. The create modal opens with every selected ticket listed under Related tickets.
If you leave the priority empty, the tracker takes the highest priority among the tickets you link.

Open the tracker’s Incident tab and add tickets from the linked tickets list. Search for the affected tickets and click Link.
Each ticket belongs to one incident at a time. If you link a ticket that’s already part of another incident, Ravenna asks Move to this incident? Click Move to relink it to the new tracker.

Work the incident

Incident tab on the tracker

The tracker shows an Incident tracker header with the number of open and total linked tickets. Its Incident tab lists every linked ticket.
Each linked ticket shows a Part of incident header with the tracker’s ID and title.
When you change the tracker’s status or priority, Ravenna applies the same change to every open linked ticket. This happens whether you update the tracker from the web app, Slack, a workflow, or MCP. Other fields, such as assignee and tags, stay independent on each linked ticket.
The tracker’s message box has a Send to all linked tickets checkbox. It’s on by default. When you send a public reply with it checked, Ravenna posts a copy of the reply on every open linked ticket. Clear it to reply on the tracker only. Each requester is notified through their own ticket’s channel, such as Slack or email. Private notes stay on the tracker.

Manage incidents with MCP

Your MCP client can create trackers and link tickets with the . With Link tickets to incident, you can also make a ticket you already opened for the incident, such as the outage, the tracker. Name that ticket as the tracker and list the affected tickets. The ticket becomes the tracker when the first ticket is linked to it, and keeps its messages, fields, and type.

Make an existing ticket the incident tracker for related tickets.


Linking rules

  • Each ticket belongs to one incident at a time.
  • Linked tickets point at one tracker, and trackers stay at the top level instead of joining another incident.
  • Merged tickets stay out of incidents: link and promote only tickets that haven’t been merged into another ticket.
  • Status changes, priority changes, and broadcasts reach open linked tickets.
  • A tracker’s form is locked. A ticket that becomes a tracker when you first link a ticket to it keeps its existing form as a read-only record.
Last modified on November 12, 2026