Prerequisites for Creating a Connection

You must satisfy the following prerequisites to create a connection with the Jira Adapter:

Purchase a Jira Subscription

When you subscribe to Jira, you receive a Jira instance URL, username, and password. This information is required for creating a Jira Adapter connection in Oracle Integration.

Prerequisites to Use the Basic Authentication Security Policy

If you want to use the Basic Authentication security policy with your Jira Adapter connection, you must perform the following prerequisites.

Create an API Token

  1. Log in to your Atlassian account using the URL:
    https://id.atlassian.com
  2. Click Account Settings.
  3. Click Security.
  4. Under API token, click Create and manage API tokens.
  5. Click Create API token.
  6. Enter a label and click Create. The API token is generated.
  7. Copy the value. You'll need to enter this value in the Password field when you configure security for your Jira Adapter connection in Oracle Integration. See Configure Connection Security.

Prerequisites to Use the Authorization Code Credentials Security Policy

If you want to use the Authorization Code Credentials security policy with your Jira Adapter connection, you must perform the following prerequisites.

Create an App and Obtain the Client ID and Client Secret

  1. Log in to your Atlassian account using the following URL:
    https://id.atlassian.com
  2. Click your profile icon and select Developer console.
  3. On the My apps page, click Create, and select OAuth 2.0 integration.
  4. Enter a name for your app, select the I agree checkbox, and click Create. A new app is displayed in the My apps list.
  5. Select your app.
  6. In the left menu, click Settings.The client ID and client secret are displayed in the Authentication details section.
  7. Copy the values for your client ID and client secret. You'll need to enter these values on the Connections page when you configure security for your Jira Adapter connection. See Configure Connection Security.

Configure the OAuth 2.0 Authorization Code and Assign the Scopes

  1. Open the app that you created in Jira.
  2. In the left menu, click Authorization.
  3. In the Callback URL field, enter the callback URL.
  4. In the left menu, click Permissions.
  5. Click Add next to the API you want to assign to your app.

Minimum Scopes for Creating a Connection

These are the minimum scopes required to configure a Jira Adapter connection in an integration. Ensure that the scopes you want to provide are configured in the Jira application.

Minimum scopes to configure the Jira Adapter as a trigger connection:
  • Minimum classic scopes:
    read:jira-work manage:jira-webhook

    Note:

    • Jira recommends using the classic scopes.
    • Use the granular scopes only when you can't use classic scopes.
  • Minimum granular scopes:
    Event Type Required Scopes
    Issue Created
    • write:webhook:jira
    • write:issue:jira
    • read:webhook:jira
    • read:issuemeta:jira
    • read:field-configuration:jira
    • read:avatar:jira
    • read:issue-details:jira
    • read:field.default-value:jira
    • read:field.option:jira
    • read:field:jira
    • read:group:jira
    • read:project:jira
    • delete:webhook:jira
    • read:jql:jira
    Issue Updated
    • write:webhook:jira
    • read:webhook:jira
    • delete:webhook:jira
    • read:field:jira
    • read:project:jira
    • read:issue-meta:jira
    • read:avatar:jira
    • read:field-configuration:jira
    • read:issue-details:jira
    • read:field.default-value:jira
    • read:field.option:jira
    • read:group:jira
    • write:issue:jira
    • read:jql:jira
    Comment Created
    • write:webhook:jira
    • read:webhook:jira
    • read:issue-meta:jira
    • read:field-configuration:jira
    • read:group:jira
    • read:project:jira
    • read:project-role:jira
    • read:user:jira
    • read:avatar:jira
    • read:issue-details:jira
    • read:field.default-value:jira
    • read:field.option:jira
    • read:field:jira
    • delete:webhook:jira
    • read:jql:jira
    • read:comment.property:jira
    • read:comment:jira
    • read:epic:jira-software
    • read:issue.property:jira
    • read:issue-type:jira
    • read:role:jira
    • read:status:jira
    Comment Updated
    • read:issue-meta:jira
    • read:avatar:jira
    • read:field-configuration:jira
    • write:comment:jira
    • write:comment.property:jira
    • write:attachment:jira
    • read:issue:jira
    • read:attachment:jira
    • read:user:jira
    • read:application-role:jira
    • read:comment:jira
    • read:comment.property:jira
    • read:project-role:jira
    • read:issue-security-level:jira
    • read:issue.vote:jira
    • read:issue.changelog:jira
    • read:status:jira
    • delete:comment:jira
    • delete:comment.property:jira
    • delete:attachment:jira
    • delete:issue:jira
    • read:issue.transition:jira
    • write:issue.property:jira
    • read:issue-type:jira
    • read:project.property:jira
    • read:issue-type-hierarchy:jira
    • read:project-category:jira
    • read:project-version:jira
    • read:project.component:jira
    • write:issue:jira
    • read:group:jira
    • read:project:jira
    • read:jql:jira
    • read:issue-details:jira
    • read:field.default-value:jira
    • read:field.option:jira
    • read:field:jira
    Project Created
    • read:issue-meta:jira
    • read:avatar:jira
    • read:field-configuration:jira
    • write:webhook:jira
    • read:webhook:jira
    • delete:webhook:jira
    • write:project:jira
    • read:project:jira
    • read:field:jira
    Project Updated
    • read:issue-meta:jira
    • read:avatar:jira
    • read:field-configuration:jira
    • write:webhook:jira
    • read:webhook:jira
    • delete:webhook:jira
    • read:field:jira
    • read:issue-type:jira
    • read:project:jira
    • read:project.property:jira
    • read:user:jira
    • write:project:jira
    • write:project.avatar:jira
    • read:application-role:jira
    • read:group:jira
    • read:issue-type-hierarchy:jira
    • read:project-category:jira
    • read:project-version:jira
    • read:project.component:jira
    Project Deleted
    • read:issue-meta:jira
    • read:avatar:jira
    • read:field-configuration:jira
    • write:webhook:jira
    • read:webhook:jira
    • delete:webhook:jira
    • read:field:jira
    • delete:project:jira
Minimum scopes to configure the Jira Adapter as an invoke connection:
  • Minimum classic scopes:
    • read:jira-user
    • read:jira-work
    • write:jira-work
    • manage:jira-project
    • manage:jira-configuration

    Note:

    • Jira recommends using the classic scopes.
    • Use the granular scopes only when you can't use classic scopes.
  • Minimum granular scopes:
    Required scopes:
    • read:issue-meta:jira
    • read:avatar:jira
    • read:field-configuration:jira
    • write:comment:jira
    • write:comment.property:jira
    • write:attachment:jira
    • read:issue:jira
    • read:attachment:jira
    • read:user:jira
    • read:application-role:jira
    • read:comment:jira
    • read:comment.property:jira
    • read:project-role:jira
    • read:issue-security-level:jira
    • read:issue.vote:jira
    • read:issue.changelog:jira
    • read:status:jira
    • delete:comment:jira
    • delete:comment.property:jira
    • delete:attachment:jira
    • delete:issue:jira
    • read:issue.transition:jira
    • write:issue.property:jira
    • read:issue-type:jira
    • read:project.property:jira
    • read:issue-type-hierarchy:jira
    • read:project-category:jira
    • read:project-version:jira
    • read:project.component:jira
    • write:issue:jira
    • read:group:jira
    • read:project:jira
    • read:jql:jira
    • read:issue-details:jira
    • read:field.default-value:jira
    • read:field.option:jira
    • read:field:jira
    • read:issue-type-hierarchy:jira
    • read:project.component:jira
    • write:project:jira
    • write:project.avatar:jira
    • delete:project:jira