UiPath Documentation
integration-service
2.2510
true

Integration Service user guide

Last updated May 11, 2026

Jira authentication

Before using Jira activities or triggers, you must create a connection to your Jira Cloud instance in UiPath Integration Service.

Important:

The Jira connector only supports Jira Cloud instances. Jira Server and Data Center instances are not supported.

Supported authentication methods (Jira Cloud only)​

Authentication typeDescriptionBest for
BasicUses Atlassian Cloud email and API tokenService accounts, unattended automations.
Bring Your Own OAuth 2.0 AppUses your own OAuth app with UiPath's callback URL.Customers managing their own app and keys.

Basic​

Authenticate with Jira Cloud using an Atlassian account email and API token, passed as HTTPS basic authentication. Learn more​.

The connection runs with the same project and issue permissions as the configured Jira user.

Required fields​

FieldDescription
Site URL

The Jira site URL, for example https://your-domain.atlassian.net.

Note: Make sure to include 'https://' and no trailing '/' at the end of the URL.

UsernameAtlassian account email used to log in to Jira Cloud
API tokenJira Cloud API token associated with the account

How to generate API token​

  1. Create an API token (without scope) in Atlassian account security.​ Learn more.
  2. Copy the generated token and keep it secure for later use.
  3. In UiPath Integration Service, add a Jira connection and fill in:
    • Site URL
    • Username
    • API token​​

Token lifecycle​

For your security, tokens can last no longer than a year and can be revoked and deleted from the Atlassian account security page. Once deleted, all Integration Service calls using that token will fail with 401 Unauthorized until a new token is configured.​

Troubleshooting​

  • 401 Unauthorized: Check email and token, confirm the token exists and was copied correctly.​
  • 403 Forbidden on some operations: Confirm the Jira user has the required project permissions for the target project and issue type.​

Frequently asked questions​

Can I limit an API token to specific projects?
No. Tokens inherit all permissions of the user; limit access by configuring user/project permissions in Jira.​

Does CAPTCHA or SSO affect token-based calls?
CAPTCHA and interactive login rules apply to username/password, not API tokens; SSO still governs the account but does not block token usage. Learn more​.

How should I rotate tokens used by UiPath?
Create a new token, update the Jira connection in UiPath with the new token, validate automations, and then revoke the old token.​

Bring your own OAuth 2.0 app​

This authentication type requires you to bring your own client ID and client secret credentials.

Follow the Jira guidelines for creating your own app: OAuth 2.0 (3LO) apps. You can create your application from the Jira developer console. While setting up your own OAuth2.0 App make sure to provide the redirect/callback URL as: https://{yourDomain}/provisioning_/callback
This is recommended when automations should run under an end‑user's context and obey both OAuth scopes and that user's project permissions.​

Required fields​

FieldDescription
Site URLJira site URL, for example: https://your-domain.atlassian.net. When prompted to grant the UiPath app permissions to access Jira, make sure to select the same Jira site URL.
Client IDClient identifier for the Atlassian OAuth 2.0 (3LO) app
Client SecretSecret from the Atlassian OAuth 2.0 (3LO) app. This will be stored in UiPath Integration Service database.
Redirect URLUiPath callback URL, configured exactly in the Atlassian app
UsernameUsed in Jira login page
PasswordUsed in Jira login page

Understanding Jira scopes​

Scopes define the level of access an app can request to interact with an Atlassian product. When a connection is established and the user authorizes the app through the Jira activity (via the API), the OAuth app receives permission to perform the specified operations on the user's behalf—subject to the user's permission settings. For a complete list of available scopes, refer to the Jira scopes documentation.

The following table lists the scopes required for creating connections:

ScopeTypeDescription
read:jira-userRequiredView user information in Jira that the user has access to, including usernames, email addresses, and avatars.
read:jira-workRequiredRead Jira project and issue data, search for issues and objects associated with issues like attachments and worklogs.
write:jira-workRequiredCreate and edit issues in Jira, post comments as the user, create worklogs, and delete issues.
manage:jira-projectRequiredCreate and edit project settings and create new project-level objects (for example, versions and components).
offline_accessRequiredRefresh OAuth token automatically
manage:jira-configurationOptionalTake Jira administration actions (for example, create projects and custom fields, view workflows, and manage issue link types).
manage:jira-data-providerOptionalManage development and release information for third parties in Jira
Important:

The app must have all scopes that your connection is requesting.

How to generate credentials​

  1. Follow Atlassian's 3LO app guide.
  2. Configure the UiPath Jira callback URL from the Integration Service Jira authentication page as the redirect URI.
  3. Select the Jira Cloud scopes you need (for example read:jira-work, write:jira-work, read:jira-user).
  4. Copy Client ID and Client Secret from the Atlassian app into the UiPath Jira connection settings.

Token lifecycle​

Access tokens are short‑lived; UiPath uses refresh tokens to obtain new access tokens until the refresh token expires or is revoked.​

Revoking consent or deleting the Atlassian OAuth app invalidates tokens and requires re‑authorization from UiPath.​

Troubleshooting (OAuth)​

  • Redirect URI mismatch: Ensure the redirect URL configured in Atlassian exactly matches UiPath's callback URL.​

  • insufficient_scope or 403: Add any missing Jira scopes to the app and ensure the user has necessary Jira permissions.​

Frequently asked questions​

What are the minimum scopes to issue CRUD?
It varies from one object to another, but usually read:jira-work and write:jira-work for issues/comments; add read:jira-user if user lookup/assignment is used​.

Can scopes restrict access to specific projects?
No. Scopes are functional; project-level access is still governed by the authorizing user's permissions in Jira.​

Why do I still get 403 after a successful OAuth login?
Ensure read:jira-user is being inferred in your private app.

Add the Jira connection​

To create a connection to your Jira instance, you need to perform the following steps:

  1. Select Integration Service from the left rail.
  2. From the Connectors list, select Jira. You can also use the search bar to narrow down the connector.
  3. Select the Connect to Jira button.
  4. Select an authentication type.
  5. Enter the required credentials for your preferred authentication method and select Connect.

Permissions​

With access to your account, UiPath for Jira Cloud is able to:

  • Manage settings:
    • Take Jira administration actions (e.g. create projects and custom fields, view workflows, manage issue link types).
    • Manage development and release information for third parties in Jira.
    • Create and edit project settings and create new project-level objects (e.g. versions and components).
  • View data:
    • View user information in Jira that the user has access to, including usernames, email addresses, and avatars.
    • Read Jira project and issue data, search for issues, and objects associated with issues like attachments and worklogs.
  • Update issues:
    • Create and edit issues in Jira, post comments as the user, create worklogs, and delete issues.

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated