Skip to main content
The Jira Server integration works with self-hosted Jira, covering both Jira Server and Jira Data Center. It’s separate from the Jira integration, which connects to Jira Cloud. Connect using basic authentication or an application link from Settings → Integrations → Jira Server. Once connected, export follow-ups as Jira issues, create tickets to represent incidents, and use Jira projects, users, and priorities in your catalog.

​
Prerequisites

Before you start, make sure you have:
  • Jira administrator access, to create the application link or the service account.
  • A route from incident.io to your Jira instance. See Network access for the options.

​
Choose an authentication method

​
Basic authentication

incident.io acts as the service account in Jira, so anything it does shows up as that user. Give the account permission to browse projects, and to create, edit, assign, and link issues in the projects you plan to use.
  1. Select HTTP Basic Authentication
  2. Enter your Jira base URL, then the service account’s username and password
An application link authenticates with OAuth 1.0 and avoids storing a set of credentials in incident.io. The connect dialog generates a consumer key and public key for your account, which you paste into Jira when you create the link.
  1. Select Application Link (OAuth 1) and follow the steps shown, which include the values to paste into Jira
  2. Enter your Jira base URL and select Connect to authorize the link in Jira

​
Sync changes back from Jira

Register a webhook in Jira so updates to exported issues reach incident.io quickly. See Setting up a webhook in Jira Server.

​
Network access

How you connect depends on where your Jira runs:
  • Reachable from the internet: allow inbound traffic from our IP addresses.
  • Private network: route our requests through a proxy instead of exposing the instance.
  • Internal certificate authority: paste your CA certificate into the connect dialog so we trust the certificate Jira presents.