Overview
Jira can be connected in three ways:- Personal API token
- Service account API token
- Service account OAuth client credentials
Option 1: Personal API Token
Personal API token gives access to Jira as that Atlassian user and is the only Jira option that currently supports managed webhook registration. Create an Atlassian API token for that user at Atlassian API tokens, then connect in Mistle with:| Field | Value |
|---|---|
site_url | Jira Cloud site URL like https://your-site.atlassian.net |
email | Atlassian account email |
apiKey | Atlassian API token |
Option 2: Service Account API Token
Service account API token gives access to Jira as a service account by using a scoped Atlassian API token. Create a service account and a scoped API token, then connect in Mistle with:| Field | Value |
|---|---|
cloud_id | Jira Cloud ID |
apiKey | Service account API token |
cloud_id, not a site URL. Atlassian’s scoped service-account tokens use the api.atlassian.com/ex/jira/<cloudId>/... API shape, so make sure you collect the cloud ID before connecting.
Option 3: Service Account OAuth Client Credentials
Service account OAuth client credentials gives access to Jira as a service account by exchanging a client ID and client secret for access tokens. Create Atlassian OAuth 2.0 credentials for the service account, then connect in Mistle with:| Field | Value |
|---|---|
cloud_id | Jira Cloud ID |
client_id | Atlassian OAuth client ID |
clientSecret | Atlassian OAuth client secret |
Webhooks
Managed webhook registration is currently supported only for personal API token connections. After the connection exists, use the Webhooks section on that connection. The product already shows the callback URL to copy into Jira, and the managed webhook registration can be created from there.Jira Cloud
The current Jira integration is Jira Cloud only. The connection schemas require Atlassian Cloud values such as*.atlassian.net site URLs and cloud_id.