Configuring Jira Notifications

Overview

Configuring the Jira integration in DefensX consists of the following steps:

  • Create a Jira API token from your Atlassian account

  • Assign the token to the Jira app with required scopes

  • Copy and securely store the API token

  • Configure Jira connection settings in DefensX

  • Define the Jira issue template

  • Select events and customers

  • Activate the integration

WARNING: Jira API tokens are displayed only once during creation. If the token is lost, it must be revoked and recreated.

Creating a Jira API token

Before creating a Jira integration in DefensX, you need to generate an API token from your Atlassian account.

API tokens are managed from the following page:

https://id.atlassian.com/manage-profile/security/api-tokens

Step 1: Start API token creation

  • Open the API Tokens page

  • Click on Create API token with scopes

jira 1

Step 2: Name the API token

  • Enter a descriptive name for the token Example: DefensX_Jira_Integration

  • Select an expiration date Tokens can last no longer than 365 days

jira 2

Step 3: Select the app

  • From the app list, select Jira

  • This ensures the token can only access Jira APIs

jira 3

Step 4: Select Jira scopes

  • Search for jira-work

  • Select the following scopes: read:jira-work, write:jira-work

These scopes allow DefensX to read Jira projects and issues and to create or update issues when required.

jira 4

Step 5: Review the API token

  • Verify the token name

  • Confirm the expiration date

  • Check the selected app and scopes

  • Click Create token

jira 5

Step 6: Copy and save the API token

  • Copy the generated API token

  • Store it in a secure location

WARNING: You will not be able to view this API token again after completing this step.

jira 6

Configuring Jira integration in DefensX

After creating and saving your Jira API token, you can configure the Jira integration in DefensX.

This configuration allows DefensX to automatically create Jira issues for selected events.

Connection Details

This section defines the Jira credentials DefensX uses to communicate with Jira.

  • Cloud ID

  • Email

  • API Token

jira 7

Cloud ID

The Cloud ID is a unique identifier for your Jira Cloud instance. DefensX uses this value internally to construct Jira REST API endpoints.

To retrieve your Cloud ID, open the following URL in your browser and replace yourcompany with your Jira domain:

https://yourcompany.atlassian.net/_edge/tenant_info

The response will be a JSON document similar to the following:

{
  "cloudId": "abc123-def456-ghi789"
}

  • Copy the value of cloudId

  • Paste it into the Cloud ID field in DefensX

Email

The email address of the Atlassian user who created the Jira API token.

This email is used together with the API token to authenticate requests sent from DefensX to Jira.

API Token

The Jira API token generated from the Atlassian account.

Issue Body

The Issue Body defines the exact JSON payload sent to Jira during issue creation.

DefensX sends this payload as-is after resolving placeholders.

You can use placeholders to dynamically insert event data:

  • {{summary}} - Jira issue title generated by DefensX

  • {{description}} - Detailed issue description with event data

Required fields

  • project.key The Jira project key where the issue will be created

  • issuetype.id The numeric ID of the Jira issue type

Optional fields

  • reporter.id Jira user ID to be set as reporter (optional)

Events, Customers and Activation

Next, you can choose which DefensX events will create Jira issues and which customers under your Partner account will be included. If you select the All Customers option, Jira issues will be created for all existing customers as well as any customers added in the future. You can also enable additional options such as adding a Custom URL Group shortcut and activate the integration to start receiving Jira issues.

jira 9

Saving the configuration

  • Review all fields

  • Click Create External Notification

Once saved, DefensX will automatically create Jira issues for selected events.