Jira authentication

You can authenticate with Jira in multiple ways, and you require the following credentials:

OAuth 2.0 Authorization Code

Required credentials:

• Site URL - The URL of your Jira instance. The site URL should have a format similar to the following: https://company.atlassian.net.
• Scope - Scopes enable an app to request a level of access to an Atlassian product. Once the connection is established and the user grants authorization via the API through the Jira activity, the OAuth app gains permission to perform the specified operations on behalf of the user, subject to the user's permission settings. For the list of scopes that can be provided please visit this page

  During the creation of a connection, you have the option to either retain the displayed scopes as they are or specify a comma-separated list of scopes of your preference. This allows you to prevent the OAuth app from automatically requesting all scope permissions by default.

  For more information, visit Scopes for Apps.

After providing the information specified above, you will have to log in to your Atlassian account using your Email and Password.

Bring your own OAuth 2.0 app

This authentication type is similar to the OAuth 2.0 Authorization Code, the difference being that you need to provide your own Client ID and Client Secret credentials.

Note:

While setting up your own Oauth2.0 App please make sure to provide the redirect/callback url as

https://cloud.uipath.com/provisioning_/callback.

Please follow the Jira guidelines for creating your own app: OAuth 2.0 (3LO) apps and you can create your own app from the Jira developer console

You can read more on this authentication type here.

Required credentials:

• Client ID
• Client Secret
• Site URL - The URL of your Jira instance. The site URL should have a format similar to the following: https://company.atlassian.net.
• Scope - Scopes enable an app to request a level of access to an Atlassian product. Once the connection is established and the user grants authorization via the API through the Jira activity, the OAuth app gains permission to perform the specified operations on behalf of the user, subject to the user's permission settings. For the list of scopes that can be provided please visit this page

  During the creation of a connection, you have the option to either retain the displayed scopes as they are or specify a comma-separated list of scopes of your preference. This allows you to prevent the OAuth app from automatically requesting all scope permissions by default.

  For more information, visit Scopes for Apps.

Basic

This authentication type requires you to generate your own API token. You can read more on how to do this here.

Required credentials:

• Site URL - The URL of your Jira instance. The site URL should have a format similar to the following: https://company.atlassian.net.
• Username - Your Jira Username.
• API Token - The token you have generated for you Jira instance.

Permissions

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

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