SEE ALSO:
Jira Cloud connector now supports OAuth 2.0 Authorization Code method.
Workflow api is unavailable with OAuth 2.0 Authorization Code that makes impossible to use custom entity states JS mapping using.
To use it in Targetprocess integrations, first, you need to create an application in Jira Cloud.
1. Navigate to https://developer.atlassian.com/console/myapps
2. Click Create and choose to add a new OAuth 2.0 integration app.
3. Navigate to Permissions to configure scopes.
4. The following 13 scopes are absolutely required. They will have to be pasted in Targetprocess profile configuration. 14th scope, 'offline_access' must be added in Targetprocess configuration
Scopes types in Targetprocess Integration profile cannot list more or other scopes than selected in OAuth Integration app in Jira Cloud. The only exception here is 'offline_access' scope that must be always added on Targetprocess side.
| Scope | Scope type | Jira explanation | Targetprocess comment |
| offline_access | To get a refresh token in your initial authorization flow, add offline_access to the scope parameter of the authorization URL. Once you have the refresh token, exchange it for an access token by calling the token URL. | This scope is required for refresh token mechanism, oherwise refreshing the access token and authentication will fail. | |
| read:jira-work | Classic scopes | View Jira issue dataRead Jira project and issue data, search for issues and objects associated with issues like attachments and worklogs. | |
| write:jira-work | Classic scopes | Create and manage issues. Create and edit issues in Jira, post comments as the user, create worklogs, and delete issues. |
|
| manage:jira-project | Classic scopes | Manage project settings Create and edit project settings and create new project-level objects (for example, versions and components). |
Scope is required for JS mappings for Components that creates new components automatically |
| manage:jira-configuration | Classic scopes | Manage Jira global settings Take Jira administration actions (for example, create projects and custom fields, view workflows, and manage issue link types). |
Required to get issue types, fields and relations |
| read:jira-user | Classic scopes | View user profilesView user information in Jira that the user has access to, including usernames, email addresses, and avatars. | Without this scope jira sends 403 forbidden code |
| Scopes for work with boards and sprints: | |||
| read:board-scope:jira-software | Granular scopes | View boards, backlogs, and related itemsView boards, issues on a board, issues from a backlog, reports, and versions. | |
| read:project:jira | Granular scopes | View projects | |
| read:board-scope.admin:jira-software | Granular scopes | View board configurationView the configuration, project features, filters, properties, and quick filters for a board. | |
| read:sprint:jira-software | Granular scopes | View sprintsView sprints and sprint related issues and properties. | |
| write:sprint:jira-software | Granular scopes | Update and delete sprintsUpdate sprints, move issues to sprints, and update the order of sprints. | |
| read:issue-details:jira | Granular scopes | View issue detailsView issue details. | |
| read:jql:jira | Granular scopes | View JQL | |
| write:board-scope:jira-software | Granular scopes | Move issues between boards and backlogs Move issues to a backlog and from a backlog to a board. |
offline_access read:jira-work write:jira-work read:jira-user manage:jira-configuration manage:jira-project read:board-scope:jira-software read:board-scope.admin:jira-software read:project:jira read:issue-details:jira write:sprint:jira-software read:sprint:jira-software write:board-scope:jira-software read:jql:jira
5. Navigate to Authorization and click Add.
Paste Callback URL that was auto generated in Targetprocess integration profile
6. After saving Authozation > Callback URL navigate to Settings to get Client ID and Secret required for Targetprocess profile configuration
7. Go back to Targetprocess integration profile and paste ClientID, Secret and all scopes, selected in Jira app.
Now integration profile is ready to be authorized in Jira. For that you have to log in to Jira with an Integration Service User.
This user has to authorize the oauth 2.0 app for integraton and pass the token.
8. Click Authorize. At this step you must be authorized to Jira with Integration Service User. In appeared pop-up you will see authorization process, allow/deny access dialog on Jira side and authorization status.
Now you can set up Jira webhook and finish integration profile configuration.
Still have a question?
We're here to help! Just contact our friendly support team.
Find out more about our APIs, Automation Rules, Mashups and custom extensions.