Jira
Two-way Jira integration. Create tickets from incidents, and status changes in Jira sync back to Runframe automatically via webhooks.
Features
| Feature | Description |
|---|---|
| Create Jira issues | Create follow-up tickets from incidents |
| Status sync | Jira issue status syncs with Runframe via webhooks |
| Link to incidents | Jira issues are linked to their source incident |
| Transition issues | Update Jira issue status from within Runframe |
Connecting Jira
- Navigate to Integrations Hub
- Click Connect next to Jira. You'll be redirected to Atlassian to authorize
- Grant Runframe read/write access to your Jira projects
- Select the default Jira project for incident work items
Creating a Jira issue from an incident
- Open an incident in the Runframe dashboard
- Click Create Jira Issue in the sidebar
- Select the project, issue type, and fill in details
- The issue is created and linked to the incident
Status syncing
When a Jira issue status changes, Runframe is notified via webhook and updates the work item status in the incident view. This works in both directions:
- Jira to Runframe: Status transitions in Jira update the work item in Runframe
- Runframe to Jira: Transitioning a work item in Runframe updates the Jira issue
Webhook configuration
To enable two-way sync, you need to configure a webhook in Jira that sends events to Runframe.
Setup steps
- In Jira, navigate to System → Advanced Settings → WebHooks
- Click Create a WebHook
- Fill in the following fields:
| Field | Value |
|---|---|
| Name | Runframe |
| Status | Enabled |
| URL | Copy the Webhook URL from the Jira section in Integrations Hub (click Configure on the Jira card) |
| Secret | Copy the Webhook Secret from the same section |
- Scroll down to Issue related events
- In the JQL filter field, enter:
labels in (runframe, runframe-automation) - Under Issue, check:
- updated
- deleted
- Leave Exclude body unchecked (Runframe needs the JSON payload)
- Leave all other sections unchecked:
- Jira Software related events (Sprint, Board)
- Worklog, Comment, Entity property, Attachment, Issue link, Filter
- User related events
- Jira configuration related events
- Project related events
- Click Create
Why the JQL filter?
The labels in (runframe, runframe-automation) filter ensures Jira only sends webhooks for issues created by Runframe, reducing noise and keeping webhook volume low. The runframe-automation label covers older tickets created by workflow automations.
Don't forget the secret
Copy the Webhook Secret from the Jira section inside Integrations Hub in Runframe and paste it into the Secret field. This ensures webhook signatures are verified and prevents unauthorized payloads from being processed.
Use with postmortems
After a postmortem, create Jira issues for each action item to ensure follow-through. Action items linked to Jira issues show their real-time status in the postmortem view.
Troubleshooting
| Issue | Solution |
|---|---|
| OAuth error during connection | Verify you have Jira admin permissions |
| Issues not syncing | Check webhook status in Jira admin settings |
| Wrong project appearing | Update default project in Runframe integration settings |
| Permission denied | Ensure Runframe has read/write access to the project |