Jira Adapter Restrictions

Note the following Jira Adapter restrictions.

• The Jira Adapter only supports Jira Cloud. Jira Server is not supported.
• The Jira Webhooks JQL configuration (for trigger connections) has the following restrictions:

  Note:

  The following restrictions apply only to integrations created prior to the Oracle Integration 22.12 release. From the 22.12 release onwards, you can build multiple Jira trigger integrations using a single connection and activate them.

  • Only one webhook listener URL is allowed, per connected application per tenant. Therefore, if you want to configure multiple Jira inbound integrations, you must create multiple connections.
  • The webhook expiration period is 30 days from the time the webhook was created. See Webhook expiration. If the Jira Adapter webhook integration does not process any notifications for more than 30 days, reactivate the integration.
  • Before you migrate (import/export) a Jira trigger integration (IAR) file from one Oracle Integration instance to another instance, you must deactivate the Jira trigger integration in the Oracle Integration instance. Select the Delete Event Subscription checkbox in the dialog that appears when you click the deactivate icon to deactivate the integration.
  • There are other restrictions. See Supported JQL Queries.

Note:

There are overall service limits for Oracle Integration. A service limit is the quota or allowance set on a resource. See Service Limits.