Available now
Jira + OnCallReady: AI Incident Response for Jira Ticket Creation
OnCallReady automatically creates Jira tickets when incidents occur — pre-populated with the full event timeline, runbook used, every action taken, duration, and resolution status — so your team has a complete audit trail without anyone typing a word at 3 AM.
How it works
When an incident resolves (or escalates), OnCallReady calls the Jira REST API to create a ticket in your chosen project. The ticket is fully formed on creation — no follow-up required.
Alert fires → OnCallReady resolves (or escalates)
│
▼
OnCallReady calls Jira REST API POST /issue
│
▼
Jira ticket created — pre-filled:
• Summary: "[Automated] Disk Full on prod-web-02 — Resolved"
• Type: Incident (or Bug — configurable)
• Priority: mapped from alert severity
• Labels: ["on-call", "auto-resolved", "disk-full"]
• Description: full timeline + actions + resolution evidence
• Resolution: Done (if auto-resolved) / Open (if escalated)
• Custom fields: runbook_id, duration_seconds, automated: true
What a generated ticket looks like
03:47:01Alert received: disk.in_use = 94% on prod-web-02
03:47:01Runbook matched: disk-full-remediation (confidence: 99%)
03:47:03Action: identify top disk consumers → /var/log/nginx (8.2GB)
03:47:12Action: rotate logs older than 7 days → freed 6.4 GB
03:47:22Action: purge /tmp files → freed 2.1 GB
03:47:29✓ RESOLVED — disk.in_use = 61% · 0 humans paged
Signal → Action table
| Incident type |
Jira ticket content |
Ticket state on creation |
| Auto-resolved incident |
Full timeline, runbook, actions, duration, before/after metrics |
Done — no human action needed |
| Escalated incident |
Diagnostic context, attempted actions, failure reason, suggested next steps |
Open — assigned to on-call |
| Recurring incident (same host, 3rd time in 7 days) |
Recurrence flag, pattern analysis, link to prior tickets |
Open — flagged for engineering review |
| P1/P2 manual incident |
Real-time timeline as engineer works, AI-drafted post-mortem in description |
In Progress until manually closed |
| Failed runbook execution |
Actions attempted, error output, environment state at failure |
Open — High priority |
Setup in 3 minutes
Create a Jira API token, set three environment variables, and every incident gets a ticket automatically.
# Add to OnCallReady environment:
JIRA_BASE_URL=https://yourcompany.atlassian.net
JIRA_API_TOKEN=your_api_token_here # from id.atlassian.com → API tokens
JIRA_USER_EMAIL=oncall-bot@yourcompany.com
JIRA_PROJECT_KEY=OPS # your ops/incidents project
JIRA_ISSUE_TYPE=Incident # or Bug, Task — whatever fits your workflow
JIRA_CREATE_ON_RESOLVE=true
JIRA_CREATE_ON_ESCALATE=true
JIRA_LABEL_AUTOMATED=auto-resolved
# That's it. Every incident — resolved or escalated —
# generates a fully-formed Jira ticket automatically.
What stays on-call
The Jira integration is purely additive — it creates records, it doesn't make decisions. These scenarios still require human attention:
- Escalated incidents create Open tickets — a human must still resolve the underlying problem
- Recurring incidents (3+ in 7 days) get flagged — engineering review needed for root cause
- Post-mortem review — OnCallReady drafts it, but a human should verify before publishing
- Ticket triage and sprint planning — OnCallReady creates, your team prioritizes
- Custom field mapping beyond the defaults — requires one-time configuration by your Jira admin
Related
Jira works best when paired with Slack for real-time comms:
Stop writing incident tickets by hand
Complete audit trail, zero manual effort. Free plan includes Jira integration.