Jira Data Center Destination (Beta)
Configuring Jira Data Center as an alert destination in your Panther Console
Last updated
Was this helpful?
Configuring Jira Data Center as an alert destination in your Panther Console
Last updated
Was this helpful?
Destinations are integrations that receive alerts from rules, policies, system health notifications, and rule errors. Panther supports configuring self-hosted 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 .
This integration authenticates with your Jira instance using a —you will create one below, in . 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.
In your Jira console, navigate to the User Management page.
Click Create user.
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.
Click Create user.
Log in as this newly created user and proceed to the next step.
In your Jira console, navigate to your user profile.
In the left-hand navigation bar, click Personal Access Tokens.
In the Token Name field, enter a descriptive name.
Click Create.
In the left-hand navigation bar of your Panther Console, click Configure > Alert Destinations.
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.
Click Jira Data Center.
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.
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.
Click Continue.
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.
If set to OFF: Specify the Labels and Priority for all Jira issues created by Panther.
Click Add Destination.
On the final page, optionally click Send Test Alert to test the integration. When you are finished, click Finish Setup.
It is recommended to be logged in as the user you created during the .
Click Create token.
Under Expiry Date, uncheck the Automatic expiry checkbox.
Copy your personal access token, and store it in a secure location. You will need it in the next step.
It is recommended to use the email address of the user created during the .
For more information on alert routing order, modifying or deleting destinations, and workflow automation, please see the Panther docs: .
