# Command Reference

Everything you need to manage incidents directly from Slack. All commands start with `/incident`

### Start an Incident

Begin tracking a new incident. Optionally specify a severity level (sev1, sev2, sev3, sev4). This creates a new incident record, timestamps the start, and notifies your team.

`/incident start [severity] <title>`

**Example**  
`/incident start sev2 Database connection timeout affecting checkout`

- Creates a new incident with a unique ID  
- Records the exact start time  
- Optionally set severity (sev1-sev4)  
- Notifies relevant team members

### Change Severity

Change the severity level of the current incident. Use this when the impact changes during an ongoing incident.

`/incident severity <level>`

**Example**  
`/incident severity sev1`

- Update severity mid-incident  
- Supports sev1, sev2, sev3, sev4  
- Logs severity change in timeline  
- Helps prioritize response efforts

### Log a Status Update

Add a timestamped update to the incident timeline. Use this to document what's happening as you investigate and resolve the issue.

`/incident status <description>`

**Example**  
`/incident status Identified slow query in orders table`

- Adds entry to incident timeline  
- Automatically timestamps the update  
- Captures who posted the update  
- Visible to all team members

### Resolve the Incident

Mark the current incident as resolved. This records the end time and calculates the total incident duration.

`/incident resolve`

**Example**  
`/incident resolve`

- Marks incident as resolved  
- Records the resolution time  
- Calculates total duration  
- Incident remains in history for review

### List Incidents

View a list of recent incidents in your workspace. Shows severity level and duration for each incident.

`/incident list`

**Example**  
`/incident list`

- Shows recent incidents  
- Displays severity levels  
- Shows incident duration  
- Quick overview of incident history

### View Analytics

**Pro**  
View incident analytics for your workspace. Defaults to 30 days, or specify a custom number of days (e.g., 7 for weekly stats).

`/incident analytics [days]`

**Example**  
`/incident analytics 7`

- View incident trends over time  
- See mean time to resolution  
- Track incidents by severity  
- Customizable time range

### Generate Postmortem

**Pro**  
Use AI to generate a comprehensive postmortem report from the incident timeline. Includes summary, root cause analysis, timeline, and action items.

`/incident postmortem`

**Example**  
`/incident postmortem`

- AI analyzes the full timeline  
- Generates root cause analysis  
- Suggests action items  
- Creates blameless, structured report

### Configure Jira Integration

**Pro**  
Connect your Jira instance to create tickets directly from Slack. You'll need your Atlassian cloud URL, project key, email, and API token.

`/incident config jira <cloud-url> <project-key> <email> <api-token>`

**Example**  
`/incident config jira your-org.atlassian.net PROJECT-KEY your@email.com your-api-token`

- Connects to your Jira Cloud instance  
- Securely stores your credentials  
- One-time setup per workspace  
- Works with any Jira project

### Create Jira Ticket

**Pro**  
Create a Jira ticket for the current incident. Automatically includes incident details, timeline, and links back to the Slack conversation.

`/incident ticket`

**Example**  
`/incident ticket`

- Creates ticket in configured project  
- Includes incident summary  
- Links to Slack conversation  
- Returns ticket URL in Slack

### Upgrade to Pro

Upgrade your workspace to Pro to unlock AI-powered postmortems, Jira integration, Markdown export, and more.

`/incident upgrade`

**Example**  
`/incident upgrade`

- View current plan status  
- Access upgrade options  
- Unlock Pro features instantly  
- Manage your subscription

## Quick Reference

Copy and paste these commands to get started.

`/incident start [severity] <title>`  
`/incident severity <level>`  
`/incident status <description>`  
`/incident resolve`  
`/incident list`  
`/incident analytics [days]`  
`/incident postmortem`  
`/incident config jira <cloud-url> <project-key> <email> <api-token>`  
`/incident ticket`  
`/incident upgrade`

## Ready to try it out?

Add Incident/Ops to your Slack workspace and start managing incidents in seconds.