# Jira Data Center Destination

## Overview

Destinations are integrations that receive alerts from rules, policies, system health notifications, and rule errors. Panther supports configuring self-hosted [Jira Data Center](https://www.atlassian.com/enterprise/data-center/jira) as the destination where you will receive alerts.

When an alert is forwarded to a Jira Data Center destination, a bug, story, or task is created in the specified project with the specified assignee.

This page explains how to set up a Jira Data Center destination. See the [instructions for setting up a Jira Cloud destination here](/alerts/destinations/jira.md).

## How to set up Jira Data Center alert destinations in Panther

### Prerequisite (recommended): Create a Jira user to represent updates from Panther

This integration authenticates with your Jira instance using a [personal access token](https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html)—you will create one below, in [Step 1](#step-1-create-a-personal-access-token-in-jira-data-center). All Jira tickets originating from Panther will display as having been created by the user who owns this access token. As such, it is recommended to first create a new Jira user (with a descriptive name) solely for this purpose, and then use that user to create the access token.

{% hint style="info" %}
To complete this prerequisite, you must be logged in as a Jira user who has permissions to create users.
{% endhint %}

1. In your Jira console, navigate to the **User Management** page.
2. Click **Create user**.
3. On the **Create a new user** page, fill in the form:

   * **Email address**: Enter a unique email address a Jira administrator will have access to.
   * **Full name**: Enter a descriptive name, e.g. `Panther Bot`.
   * **Username**: Enter a descriptive name, e.g. `pantherbot`.
   * **Password**: Enter a password an administrator will be able to use to authenticate with.
   * **Send notification email**: This field can be unchecked.
   * **Application access**: Select **Jira Software**.

   <div align="left"><figure><img src="/files/ig9s9H5KDOL6kzV6WrAl" alt="A &#x22;Create new user&#x22; form is shown, with various fields, including &#x22;Email address,&#x22; &#x22;Full name,&#x22; and &#x22;Username.&#x22; At the bottom is a &#x22;Create user&#x22; button." width="290"><figcaption></figcaption></figure></div>
4. Click **Create user**.
5. Log in as this newly created user and proceed to the next step.

### Step 1: Create a personal access token in Jira Data Center

1. In your Jira console, navigate to your user profile.
   * It is recommended to be logged in as the user you created during the [Prerequisite](#prerequisite-recommended-create-a-jira-user-to-represent-updates-from-panther).
2. In the left-hand navigation bar, click **Personal Access Tokens**.
3. Click **Create token**.\
   ![A Jira Software screen is shown, opened to a "Personal Access Tokens" page. At the bottom is a "Create token" button.](/files/omtcJk14PXdTgf1u8bMA)
4. In the **Token Name** field, enter a descriptive name.
5. Under **Expiry Date**, uncheck the **Automatic expiry** checkbox.\
   ![A "Create a personal access token" form is shown. There are various fields, such as "Token Name," and "Automatic expiry," and at the bottom is a "Create" button.](/files/oo0KAXSM6yQrkIf6Tw1b)
6. Click **Create**.
7. Copy your personal access token, and store it in a secure location. You will need it in the next step.\
   ![Above a field with a blurred-out value is a header reading "New personal access token created." Under the field is a "Close" button.](/files/WMbaqjIC0QRsTKUYqrri)

### Step 2: Configure the Jira Data Center alert destination in Panther

1. In the left-hand navigation bar of your Panther Console, click **Configure > Alert Destinations**.
2. Click **+Add your first Destination**.
   * If you have already created Destinations, click **Create New** in the upper right side of the page to add a new Destination.
3. Click **Jira Data Center**.
4. Fill out the form:
   * **Display Name**: Enter a descriptive name.
   * **Organization Domain**: Enter your organization's Jira domain (e.g. <https://jira.example.com>).
   * **Issue Type**: Enter the Jira Issue Type you would like to created. This can be `Bug`, `Story`, `Task`, or any custom type.
   * **Project Key**: Enter the Jira project identifier within your organization.
     * You can find this in Jira in your project settings page, or by browsing your organization's Jira projects and locating the `key` column.
   * **Email**: Enter the email address of the Jira user who has permissions to create the new issues with the corresponding Jira API Key.
     * It is recommended to use the email address of the user created during the [Prerequisite](#prerequisite-recommended-create-a-jira-user-to-represent-updates-from-panther).
   * **Jira API Token**: Enter the API token you generated in the earlier steps of this documentation.
   * **Severity Levels**: Select the severity level of alerts to send to this destination.
   * **Default Alert Types**: Select the alert types to send to this destination.
   * **Log Types**: By default, we will send alerts from all log types. Specify log types here if you want to only send alerts from specific log types.
   * **Allow Manual Dispatch**: Set this toggle ON if you'd like to be able to [manually dispatch alerts](https://docs.panther.com/alerts#manual-alert-dispatch) to this destination.\\

     <figure><img src="/files/G12wsLYryhgK52EMFvPD" alt="Under a title reading &#x22;Configure your Jira Data Center Destination&#x22; is a form with various fields, including Display Name, Issue Type, and Severity." width="375"><figcaption></figcaption></figure>
5. Click **Continue**.

### Step 3: Configure Jira issue properties

1. On the **Configure Jira Issue Properties** page, fill out the form:

   * **Assignee Username**: Select the user that issues will be assigned to.
     * The users available in this dropdown field are pulled from your Jira instance.
   * **Label and prioritize issues based on severity level**: Enable this if you would like to apply labels and a priority level in Jira based on alert severity in Panther. If disabled, you can still set labels and a priority level globally i.e., not based on severity). The labels and priority levels available in these dropdown are pulled from your Jira instance. If you create a new label in the **Labels** dropdown, it will also be created in your Jira instance.

     * If set to **ON**: For each severity level, specify the **Labels** and **Priority**.

     <figure><img src="/files/61iy2Z8ixtNNlp2vuIAh" alt="A &#x22;Label and prioritize issues based on severity level&#x22; toggle is shown as ON. Underneath is a list of Panther severity levels. Each one has an arrow to a Labels field and Priority field." width="563"><figcaption></figcaption></figure>

     * If set to **OFF**: Specify the **Labels** and **Priority** for all Jira issues created by Panther.

   <figure><img src="/files/yUBPV4F0P5C4HJkjqB0N" alt="A &#x22;Label and prioritize issues based on severity level&#x22; toggle is shown as OFF. Under it are two form fields: Labels and Priority." width="563"><figcaption></figcaption></figure>
2. Click **Add Destination**.
   * On the final page, optionally click **Send Test Alert** to test the integration. When you are finished, click **Finish Setup**.

## Additional Information on Destinations

For more information on alert routing order, modifying or deleting destinations, and workflow automation, please see the Panther docs: [Destinations](https://docs.panther.com/destinations).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.panther.com/alerts/destinations/jira-data-center.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.