The integration supports OAuth 2.0, API Token or Personal Access Token.

API Token

• Connection name Give this Jira connection a unique name that identifies which Jira instance it is connected to.
• Host name Complete Jira instance URL used to log in to Jira.
• API token authentication? Set this to 'Yes' to authenticate using API tokens. You must then provide an email and API token. Set this to 'No' to authenticate using basic authentication with password.
• Email Email of Jira account to link to Cequence UAP.
• API token To create an API token from your Atlassian account, use this guide: API Tokens

OAuth 2.0

OAuth 2.0 has the following limitations:

• OAuth 2.0 does not support real-time triggers.
• OAuth 2.0 is incompatible with webhook-based triggers.

Complete the following steps to authenticate through OAuth 2.0:

1. Select OAuth 2.0 as the authentication type and enter your Jira Service Desk subdomain.
2. Select advanced settings and select the authorization scopes you plan to request. Otherwise, Cequence UAP requests the following scopes by default:
   • read:jira-user
   • write:jira-work
   • manage:jira-project
   • read:jira-work
   • manage:jira-webhook
3. Click Connect and log into your Jira Service Desk instance using the account username and password in a separate window when prompted.

Authorize the request to access your Jira Service Desk instance.

Roles and permissions required to connect

Jira, Jira Cloud, and Jira Data Center users who have login access to their Jira instance can connect to UAP using their credentials. However, we recommend that a separate user (with Jira Administrator global permissions) be created for integration purposes.

Jira connection respects the project permissions schemes in your Jira project. You must ensure that your Jira account has sufficient permissions to perform the desired actions on the relevant Jira objects.

Using Jira real-time triggers

To use Jira real-time triggers, a webhook must first be registered in your connecting Jira instance. Registering webhooks to Jira instances requires Jira Administrator global permissions.

If your linked Jira account has Jira Administrators global permissions, then the UAP integration automatically registers a webhook in your Jira instance when your UAP integration recipe (containing a Jira real-time trigger) is started for the first time.

For more information on Jira administrators & global permissions, check out Jira's global permissions guide.

If your linked Jira account does not have Jira Administrators global permissions, you will not be authorized to register webhooks and will require assistance from a user with Jira administrators global permissions to register one for you.