---
title: Jira
description: Create issues in Jira and Jira Service Management.
breadcrumbs: Docs > Integrations > Jira
---

# Jira

## Overview{% #overview %}

Atlassian Jira is a project management and issue tracking tool for teams to coordinate work and handle tasks efficiently.

Integrate with Jira or Jira Service Management to:

- Create and update issues using `@jira` mentions in monitor notifications
- Receive a Datadog event each time a new Jira issue is opened
- Manually create new Jira issues
- Link new or existing Jira issues to a Datadog incident or case
- Automate Jira issue creation and send incident attributes to Jira attributes
- Automate Jira issue creation and sync case and Jira attributes

## Setup{% #setup %}

{% alert level="info" %}
Datadog highly recommends having a dedicated (non-personal) Jira service account specifically for this integration for optimal and more consistent results.
{% /alert %}

### Jira Cloud instructions{% #jira-cloud-instructions %}

#### OAuth 2.0 setup instructions{% #oauth-20-setup-instructions %}

1. Navigate to the [Datadog Jira integration tile](https://app.datadoghq.com/integrations/jira) and click **Add Account > OAuth 2.0 Account**.
1. Enter the URL of your Jira instance.
1. Click **Authenticate with Atlassian** and follow the instructions on the Atlassian authorization page. **If there is a dropdown to select which Atlassian account instance, make sure to select the same one you just entered into Datadog**.
1. Click **Accept** on the Atlassian authorization page. You are redirected back to the Jira tile, with the new account in "Pending" status.
1. The account moves to "Active" status once Datadog has verified that the account is valid and ready for use.

#### Legacy OAuth 1.0 setup instructions{% #legacy-oauth-10-setup-instructions %}

##### Create an application link in Jira{% #create-an-application-link-in-jira %}

1. Navigate to Jira.

1. Click the Gear icon in the right corner and select **Jira Apps**.

1. In the left menu under **Integrations**, click **Application links**, and then click **Create link**.

1. Select the **Direct application link** checkbox, enter the URL `https://` and click **Continue**.

1. Ignore the warning "No response was received from the URL you entered" and click **Continue**.

1. Fill in the form as follows and click **Continue**.

| Field                 | Input                           |
| --------------------- | ------------------------------- |
| Application Name      | `{Enter a name (e.g. Datadog)}` |
| Application Type      | Generic Application             |
| Service Provider Name | `{leave blank}`                 |
| Consumer key          | `{leave blank}`                 |
| Shared secret         | `{leave blank}`                 |
| Request Token URL     | `{leave blank}`                 |
| Access token URL      | `{leave blank}`                 |
| Authorize URL         | `{leave blank}`                 |
| Create incoming link  | Check the box                   |

1. Fill in the next form as follows and click **Continue**. To find the public key in the [Datadog Jira integration tile](https://app.datadoghq.com/integrations/jira), click **Add Account**.

| Field         | Input                                                       |
| ------------- | ----------------------------------------------------------- |
| Consumer Key  | `{Enter a key name (e.g. datadog)}`                         |
| Consumer Name | Datadog                                                     |
| Public Key    | `{Enter the public key from Datadog Jira integration tile}` |

##### Connect Datadog{% #connect-datadog %}

After creating the application link, connect Datadog to your Jira instance:

1. Navigate to the [Datadog Jira integration tile](https://app.datadoghq.com/integrations/jira) and click **Add Account > Legacy OAuth 1.0 Account**.
1. Enter the URL of your Jira instance and the consumer key of the application link you previously created.
1. Click **Connect** and follow the instructions on the Jira authorization page. Be sure to log into this account before hitting **Connect**.

##### Migrate tool for legacy OAuth 1.0 accounts{% #migrate-tool-for-legacy-oauth-10-accounts %}

In the Jira Accounts Table, Legacy OAuth 1.0 accounts that are eligible for migration to OAuth 2.0 have a "Migrate to OAuth 2.0" arrow button. Click this button and then click **Authenticate with Atlassian** to start the OAuth 2.0 flow. **Note**: You cannot undo this action, so make sure to select the correct Atlassian account when authenticating.

### Jira Data Center instructions{% #jira-data-center-instructions %}

{% callout %}
# Important note for users on the following Datadog sites: app.ddog-gov.com



{% alert level="info" %}
Jira Data Center's current OAuth 1.0a implementation is not FIPS 140-2 compliant. US1-FED customers should be aware of this limitation when considering the integration for FedRAMP environments.
{% /alert %}


{% /callout %}

#### Legacy OAuth 1.0 setup instructions{% #legacy-oauth-10-setup-instructions-1 %}

##### Create an application link in Jira{% #create-an-application-link-in-jira-1 %}

1. Navigate to Jira.
1. Click the Gear icon in the right corner and select **Applications**.
1. In the left menu under **Integrations**, click **Application links**, and then click **Create link**.
1. In the **Create link** dialog, select **Atlassian product** and provide the Application URL as `https://`. Click **Continue**.
1. Ignore the warning "No response was received from the URL you entered" and click **Continue**.
1. Fill in the form using the same parameters as shown in the Jira Cloud instructions above.

##### Connect Datadog{% #connect-datadog-1 %}

After creating the application link, follow the same Datadog connection steps as Jira Cloud Legacy OAuth 1.0 above.

**Note**: Many Jira Data Center instances blocklist IP ranges. For the integration to work, follow the IP filtering documentation below.

### IP filtering{% #ip-filtering %}

If your Jira instance filters traffic by IP address, you need to allow connections from the **Webhooks** IP prefixes belonging to Datadog in order for the integration to work. For a list of **Webhooks** IP prefixes for your region, see [Datadog IP Ranges](https://docs.datadoghq.com/api/latest/ip-ranges.md).

### Multiple Datadog accounts using the same Jira instance{% #multiple-datadog-accounts-using-the-same-jira-instance %}

Refer to the following instructions if you have multiple Datadog accounts that need to connect to the same Jira instance.

#### OAuth 2.0 setup{% #oauth-20-setup %}

You need a unique admin Atlassian account per Datadog account. When authorizing the connection between Jira and Datadog, make sure to log into the correct Atlassian account that corresponds to the Datadog account you are connecting. This is required to keep authorized user accounts separate in Jira for each Datadog account.

#### Legacy OAuth 1.0 setup{% #legacy-oauth-10-setup %}

You must set up multiple application links in Jira and connect each Datadog account to a different application link using a unique consumer key.

### Further configuration{% #further-configuration %}

To configure automated Jira issue creation with bidirectional syncing in Case Management, see the instructions for Configuring a Jira webhook and the [Case Management](https://docs.datadoghq.com/service_management/case_management/settings.md#jira) documentation.

To create Jira issues from Datadog monitor alerts, see Configure an issue template.

## Configure a Jira webhook{% #configure-a-jira-webhook %}

Configuring a webhook enables cases created in Case Management to automatically create issues in Jira and keep both resources synced.

To create a Jira webhook:

1. In Jira, click the **Gear** icon in the top right corner and select **System**.
1. In the left menu under *Advanced*, click **Webhooks**.
1. Click **Create a Webhook** in the right corner.
1. Enter `Datadog Webhook` as the webhook name.
1. Keep the status as **Enabled**.
1. Navigate to the [Datadog Jira integration tile](https://app.datadoghq.com/account/settings#integrations/jira).
1. Under the **Case Management** tab, copy the webhook URL.
1. Navigate back to Jira and paste the webhook URL under *URL*.
1. Enable the following issue-related events. If you only want to send a subset of issue events, you can use JQL to filter them. In this example we are filtering only for projects AB and CD.
1. Enable the `deleted` project-related events.
1. Leave everything else unchecked.
1. Click the **Create** button at the bottom of the page.

## Configure an issue template{% #configure-an-issue-template %}

Issue templates define how issues are created in Jira from Datadog alert events.

To create an issue template:

1. In Datadog, click **New Issue Template** in the **Connect Jira to Monitor Notifications** section.
1. Enter a name for your issue template. This name, prefixed with `jira-`, becomes the handle you can use in your monitor to send notifications to (such as `jira-my-issue-template-name`).
1. Select a Jira account.
1. Select the project and issue type (such as **Story**, **Epic**, **Task**, or **Bug**).
1. A list of configurable fields appears. Enter values in the desired fields and click **Save**.

### Configure issue fields{% #configure-issue-fields %}

Issue template fields define the data that is included when creating issues in Jira. For example, you can configure your template to create issues with a specific priority or a default assignee.

You can use data from the alert event to populate values in the issue fields using template variables such as `${EVENT_TITLE}`. For a list of possible variables, see the [Datadog Webhooks integration](https://docs.datadoghq.com/integrations/webhooks.md).

## Usage{% #usage %}

#### Automatically create issues from Datadog alerts{% #automatically-create-issues-from-datadog-alerts %}

To create Jira issues from Datadog alert events, enter the notification handle of one or more issue templates such as `@jira-my-issue-template` when creating a monitor in the **Notify your team** or **Say what's happening** sections.

Issues are created when the monitor triggers. New issues are not created by the monitor until the monitor is resolved.

## Data Collected{% #data-collected %}

### Metrics{% #metrics %}

The Jira integration does not include any metrics.

### Events{% #events %}

All created Jira issues appear as events within Datadog.

### Service Checks{% #service-checks %}

The Jira integration does not include any service checks.

## Troubleshooting{% #troubleshooting %}

Need help? Contact [Datadog support](https://docs.datadoghq.com/help/).