Jira Integration
Automatically create Jira issues from TigerOps incidents with AI-generated descriptions, trace links, and reproduction steps. Your dev team gets actionable context before they even open the ticket.
How It Works
Connect via Jira API Token
Generate a Jira API token from your Atlassian account settings and add your Jira site URL and project key in TigerOps. OAuth app flow is also supported.
Map Fields and Labels
Configure which Jira project receives incidents, which issue type to use (Bug, Incident, etc.), and how TigerOps severity maps to Jira priority fields.
Incidents Create Issues Automatically
When TigerOps detects a qualifying incident, it creates a Jira issue with AI-generated description, affected services, trace links, and log excerpts.
Bidirectional Status Sync
Closing a TigerOps incident can transition the Jira issue to Done. Resolving in Jira posts a comment back to TigerOps. Your workflows stay in sync.
What You Get Out of the Box
AI-Generated Issue Descriptions
Every Jira issue body includes an AI-written incident summary: what happened, what was affected, suspected root cause, and suggested next steps for the engineer.
Trace & Log Context
TigerOps embeds direct links to relevant distributed traces, error stack traces, and log excerpts in the Jira issue — giving developers everything they need to reproduce.
Custom Field Mapping
Map TigerOps metadata (service name, environment, team, severity) to any Jira custom field. Populate labels, components, fix version, and sprint automatically.
Duplicate Prevention
TigerOps uses deduplication keys to prevent creating multiple Jira issues for the same incident. If an issue already exists, TigerOps adds a comment instead.
SLA & Time Tracking
TigerOps records incident start time, detection time, and resolution time in the Jira issue — enabling accurate MTTR reporting and SLA compliance tracking in Jira.
Jira Cloud & Server
Works with Jira Cloud, Jira Software (Server/Data Center), and Jira Service Management. Both REST API v2 and v3 are supported.
Jira Issue Template
Example of the Jira issue body that TigerOps generates automatically for each incident.
# TigerOps Jira Integration Configuration
jira_integration:
site_url: "https://your-org.atlassian.net"
email: "tigerops-bot@your-org.com"
api_token: "${JIRA_API_TOKEN}"
# Default project for incident issues
default_project: "OPS"
default_issue_type: "Bug"
# Map TigerOps severity to Jira priority
severity_mapping:
critical: "Highest"
warning: "Medium"
info: "Low"
# Custom fields to populate
field_mapping:
environment: "customfield_10201"
service: "customfield_10202"
team: "customfield_10203"
# Auto-transition Jira issue when TigerOps resolves
auto_resolve:
enabled: true
transition_name: "Done"
add_resolution_comment: true
# AI-generated issue body template
issue_body_template: |
*Detected by TigerOps AI SRE at {{ .DetectedAt }}*
h2. Incident Summary
{{ .AISummary }}
h2. Affected Services
{{ range .AffectedServices }}- {{ . }}{{ end }}
h2. Key Links
- [View in TigerOps|{{ .DashboardURL }}]
- [Root Trace|{{ .TraceURL }}]
- [Related Logs|{{ .LogsURL }}]Common Questions
Does TigerOps create Jira issues for every alert or only incidents?
By default, TigerOps creates Jira issues only for incidents — which are AI-correlated groups of alerts that represent a real production problem. You can configure whether individual high-severity alerts also create issues, but the default reduces Jira noise significantly.
Can TigerOps update an existing Jira issue when an incident evolves?
Yes. If an incident worsens (more services affected, severity escalates), TigerOps adds a comment to the existing Jira issue with updated context. It does not create duplicate issues.
Does TigerOps work with Jira Service Management (JSM)?
Yes. TigerOps can create JSM service requests and incidents in addition to Jira Software issues. You can map TigerOps incident severity to JSM priority levels and route to specific JSM queues.
Can I link a Jira issue back to a TigerOps incident manually?
Yes. TigerOps provides a Jira issue link field in the incident view. Engineers can paste an existing Jira issue key and TigerOps will track the link, posting resolution updates back to that issue.
What Jira permissions does TigerOps need?
TigerOps requires a Jira user or API token with: Create Issues, Edit Issues, Transition Issues, and Add Comments permissions in the target project. We recommend a dedicated service account rather than a personal user account.
Production Issues, Auto-Filed in Jira
No credit card required. Connects in minutes. AI context included.