| Features | Standard | Advanced |
|---|
Declare, track, and resolve incidents as Jira issues in the Jira your team already uses. | | |
Dedicated incident channels, status updates, and resolution without leaving chat. | | |
SLA targets per severity for acknowledgement, validation, updates, RCA completion, and action items. | | |
Automatic nudges to acknowledge, post updates, and validate the incident, with channel cleanup when it's over. | | |
An RCA opens automatically when an incident resolves and walks the team through Five Whys to the root cause. | | |
Incidents can't close until the RCA is finished, so reviews actually happen. | | |
Follow-ups are tracked to completion so the same incident doesn't recur. | | |
Updates drafted from the incident timeline and sent in one click. | | |
Responders joining mid-incident get an instant summary of what's happened so far. | | |
AI-drafted executive summaries and help identifying root cause during review. | | |
MTTA, MTTR, uptime, and trends, plus outcomes & causes, lifecycle, and action-item reports. | | |
Reports and RCA reminders delivered automatically on a schedule. | | |
Integrates with the paging tool you already use (PagerDuty, SPlunk & Opsgenie) | | |
Built-in on-call schedules, escalations, and paging, so you can retire your separate paging tool and run on-call where incidents live. | | |