Ticketing Integrations

Auto-create tickets from incidents and keep them in sync through resolution.

Jira

Setup

  1. Go to Settings → Integrations → Jira → Connect
  2. Enter your Jira instance URL (e.g., your-company.atlassian.net)
  3. Authorize via OAuth
  4. Select the default project and issue type

Configuration

| Setting | Example | |---------|---------| | Project | OPS | | Issue type | Bug or custom Incident type | | Priority mapping | P1 → Highest, P2 → High, P3 → Medium | | Auto-create | On incident trigger or on demand | | Sync resolution | Resolving in NotifyHero closes the Jira ticket |

Bidirectional Sync

  • Incident triggered → Jira ticket created
  • Incident resolved → Jira ticket transitions to Done
  • Jira ticket closed → Incident resolved in NotifyHero
  • Notes and comments sync both ways
Incident #INC-1042 ↔ OPS-587
Status, priority, and comments stay in sync

Tip: Create a custom "Incident" issue type in Jira with fields for severity, duration, and root cause. NotifyHero populates them automatically.

Linear

Setup

  1. Go to Settings → Integrations → Linear → Connect
  2. Authorize with your Linear account
  3. Select the default team and project

Configuration

  • Team: Engineering
  • Label: incident (auto-applied)
  • Priority mapping: P1 → Urgent, P2 → High
  • Auto-create: On trigger or manual

Features

  • Auto-create Linear issues from incidents
  • Sync status: Triggered → In Progress, Resolved → Done
  • Link action items from postmortems directly to Linear issues
  • Bulk-create issues from postmortem action items

GitHub Issues

Setup

  1. Go to Settings → Integrations → GitHub → Connect
  2. Authorize the NotifyHero GitHub App
  3. Select repositories to connect

Configuration

  • Repository: your-company/api-service
  • Labels: incident, P1 (auto-applied based on priority)
  • Auto-create: On trigger or manual
  • Template: Custom issue body template

Example Auto-Created Issue

## Incident #INC-1042 — API Latency Spike

**Severity:** Critical
**Service:** api-service
**Triggered:** 2026-03-01 09:00 UTC
**Status:** Triggered

### Details
API p99 latency exceeded 2s threshold for 5 minutes.

### Links
- [NotifyHero Incident](https://app.notifyhero.com/incidents/INC-1042)
- [Grafana Dashboard](https://grafana.your-company.com/d/api-latency)

Common Settings

All ticketing integrations support:

  • Auto-create rules — create tickets for all incidents, critical only, or specific services
  • Bidirectional sync — status changes flow both ways
  • Custom field mapping — map NotifyHero fields to your ticketing fields
  • Postmortem action items — create tickets directly from postmortem follow-ups

Configure per-service rules at Service → Integrations → Ticketing Rules.