When you’d use this
- People report incidents in Jira. Support or another team files an issue, and Rubix starts looking.
- You run incidents from Jira. Mark an issue as an incident, and it gets an RCA and Tasks here.
Connect it
Make its webhook in RubixKube
Go to Environments > Connect and pick Jira. Give it a name, then choose Make its webhook. Copy the URL. It’s shown once, and anyone who has it can post to it.
Add the webhook in Jira
In Jira, go to Settings > System > Webhooks and create a webhook. Paste the URL.
What opens an incident and what resolves it
An issue counts when it has the labelincident, or when its issue type is Incident.
Severity comes from the issue’s priority: Highest is critical, High is high, Low and Lowest are low, and anything else is medium.
Editing an issue without changing its status does nothing. If you add the
incident label to an existing issue, the incident opens at its next status change.What you’ll see
The source appears on Environments as soon as you make its webhook, then shows as connected when the first message arrives. Its page has an Events tab with the last 20 messages, so you can check what Jira really sent. The automation Jira issues become incidents is on under Automations. If events arrive and no incident opens, the source page says so and offers Turn on. Each incident carries the alert’s details and a link back to Jira. Triage, the RCA and Tasks then work as they do for any other incident.What Rubix can read too
Jira is read through Atlassian Rovo, which also covers Confluence. See Atlassian Rovo.Related pages
Atlassian Rovo
Let Rubix read Jira and Confluence.
Integrations overview
The two ways to connect a tool.
Linear
The same idea for Linear.
Incidents
What happens after an incident opens.