What we can do with Jira
There are 2 main features incident.io supports with Jira:Exporting follow-ups as Jira tickets
With Jira connected to incident.io you can export follow-ups via the web dashboard and our Slack/MS Teams apps. Information on the ticket such as its title, assignee, and completion is synced back to incident.io, updating the corresponding follow-up.

Syncing incidents to Jira
When enabled, a Jira ticket will be created to represent each incident in Jira. We automatically sync the incident ticket when the incident is changed in incident.io.

Setting up
We connect to Jira as a specific user. That means that actions taken by incident.io in Jira will show up as by the connecting user. We therefore recommend you create a Jira user called something like “incident.io”, and sign in to Jira with that account before you begin (you can remain signed in to incident.io as your usual account!)- Head to Settings → Integrations → Jira
- Click on ” Connect ”: you’ll be redirected in to Jira to approve our access
We also support Jira on Atlassian GovCloud. The setup process is the same as for standard Jira Cloud instances.
Enabling multiple Jira sites
Depending on your billing plan, you may be able to enable multiple Jira sites to be used in incident.io , allowing incident.io to create tickets in multiple Jira sites. You can do this by clicking on the edit button next to the site name in the Jira integration settings page, where you will be able to enable more sites. If you don’t see the desired sites, click ” Connect another site ” to authorize access to additional sites. Note that if you’ve previously used Atlassian Connect, you’ll need to disconnect all sites and reconnect via OAuth, due to Atlassian ending support for Connect at the end of 2026.FAQs
Do you support Jira Components?
Do you support Jira Components?
Yes, Components are treated as optional fields within your template.