Linear Integration
Turn production incidents into Linear issues automatically — with AI summary, SLO context, and trace links attached. Bidirectional sync keeps your incident record in both tools.
How It Works
Connect TigerOps to Linear
In TigerOps Settings > Alerting > Linear, authorize with your Linear workspace. TigerOps gets permission to create and update issues in the teams you select.
Map Alerts to Teams & Projects
Configure routing rules that map TigerOps alert labels to Linear teams and projects. Infrastructure alerts go to the Platform team; application errors go to the relevant product team.
Auto-Create Issues with Context
When a TigerOps alert fires, a Linear issue is created with the AI-generated summary, affected service, SLO budget remaining, trace links, and runbook URL in the description.
Sync Resolution Status
When TigerOps resolves an alert, the corresponding Linear issue is automatically transitioned to "Done". Issue comments are added at each state change for full audit trail.
What You Get Out of the Box
Automatic Issue Creation
TigerOps creates Linear issues the moment an alert fires — no manual copy-paste from alert to issue. The issue title, description, and labels are populated from the alert context.
Severity & Priority Mapping
Map TigerOps severity levels to Linear priorities: Critical → Urgent, High → High, Medium → Medium, Low → Low. Custom mapping per team is supported.
SLO Context in Descriptions
Linear issue descriptions include the current SLO burn rate, error budget remaining, and a link to the TigerOps SLO dashboard for the affected service.
Label Automation
Issues are auto-labeled with the affected service name, environment, and alert category (infrastructure, application, security). Labels are pre-created in Linear on first sync.
Bidirectional Status Sync
When engineers cancel or re-open an issue in Linear, TigerOps reflects the change. When TigerOps auto-resolves, the Linear issue closes automatically.
Incident Timeline as Comments
Key incident events — detection, acknowledgement, mitigation steps, and resolution — are posted as Linear issue comments with timestamps for a complete incident record.
Integration Webhook Configuration
Map TigerOps alerts to Linear teams with custom issue templates.
# tigerops-linear-config.yaml — Linear integration settings
integrations:
linear:
apiKey: "${LINEAR_API_KEY}"
workspaceId: "${LINEAR_WORKSPACE_ID}"
routing_rules:
# Infrastructure alerts → Platform team
- match:
labels:
category: infrastructure
env: production
linear:
teamId: PLATFORM_TEAM_ID
projectId: INFRA_PROJECT_ID
priority: urgent # urgent | high | medium | low | no_priority
labels: [production, infrastructure, incident]
assignToOnCall: true
# Application errors → relevant product team
- match:
labels:
category: application
linear:
teamId: "${LABELS.team_linear_id}"
priority: high
labels: [production, application-error]
issue_template:
title: "[{{ .Severity | upper }}] {{ .AlertName }} — {{ .Service }}"
description: |
## Incident Summary
{{ .AISummary }}
## Details
- **Service**: {{ .Service }}
- **Environment**: {{ .Labels.env }}
- **Detected at**: {{ .FiredAt | formatTime }}
- **SLO burn rate**: {{ .SLOBurnRate }}
- **Error budget remaining**: {{ .SLOBudgetRemaining }}
## Links
- [TigerOps Incident]({{ .IncidentURL }})
- [Correlated Trace]({{ .TraceURL }})
- [Runbook]({{ .RunbookURL }})
auto_resolve:
enabled: true
transitionTo: doneCommon Questions
Can TigerOps create issues in multiple Linear teams from the same alert?
Yes. Configure multiple Linear routing rules to send the same alert to multiple teams — for example, creating an issue in the Platform team and a linked issue in the affected product team simultaneously.
How does TigerOps prevent duplicate Linear issues?
TigerOps uses the alert fingerprint as a deduplication key. If an alert fires multiple times within the same incident window, TigerOps adds a comment to the existing Linear issue rather than creating a new one.
Can we assign issues to specific Linear team members based on on-call schedule?
Yes. TigerOps can query your on-call schedule (from PagerDuty, Opsgenie, or the TigerOps on-call scheduler) and assign the Linear issue to the current on-call engineer automatically.
Does TigerOps support Linear sub-issues (child issues)?
Yes. For complex incidents affecting multiple services, TigerOps can create a parent incident issue and link individual per-service alert issues as sub-issues in Linear.
Can I customize the Linear issue template?
Yes. TigerOps provides a Markdown template editor for the Linear issue title and description. Use template variables like {{ .AlertName }}, {{ .Service }}, {{ .Value }}, and {{ .AISummary }} to customize the output.
Production Incidents Become Linear Issues Automatically
AI summaries, SLO context, and bidirectional sync. Stop copying from alert tools to issue trackers.