Jira Service Management (JSM) Data Connector
The BigPanda Unified Data Connector (UDC) syncs data from Jira Service Management (JSM) to provide context and insights for AI Incident Assistant (Biggy) and AI Detection and Response. Ingested data is securely stored and made available in the IT Knowledge Graph, powering accurate answers, deep analytics, trend analysis, and advanced capabilities.
Not bi-directional and monitoring incident sync
The Jira Service Management data connector does not enable incident sync and sharing from the BigPanda event monitoring incident feed. See the Jira Service Management (JSM) integration documentation for details on managing incidents with JSM in BigPanda.
JIRA and JSM Connectors
The JSM data connector enriches standard Jira issues with JSM-specific data. You must first connect a Jira project for incident management and automation. See the Jira Data Connector documentation for steps on connecting a Jira project.
For each issue, the JSM Data Connector leverages these fields for context:
SLA metrics, status history, request type, service desk name
Participants and comments
Approvals
CSAT feedback scores
Authentication
The JIRA and JSM connectors support Basic Authentication and JWT.
Basic Authentication
Credentials required for cloud instances:
Field | Description |
|---|---|
Subdomain | The subdomain of your JIRA instance in case you don’t use a scoped api token |
Username | Username of the account used to access JIRA. |
API Token | The user API token of the account used to access JIRA. If it is a scoped token make sure to include the the classic scope type |
JQL | JQL to filter the relevant JIRA projects |
Fields | Optional. If not set, all fields are retrieved. |
Cloud id | Required in case the token is scoped. In order to get the cloud id, log into atlassian with your user and browse to the page:
|
Credentials required for data center instances:
Field` | Description |
|---|---|
URL | The URL of your JIRA instance |
Username | Username of the account used to access JIRA. |
Password/ PAT | The password or the personal API token of the user used to access JIRA. |
JQL | JQL to filter the relevant JIRA projects |
Fields | Optional. If not set, all fields are retrieved. |
Atlassian JSON Web Token (JWT) authentication
If Jira or Confluence is selected as the source, you can also choose to authenticate the connection using Atlassian's JSON Web Token (JWT):
Select the Atlassian JWT radio button.
Fill in the required fields:
Key: JWT public key
Shared secret: JWT shared secret.
Sync preferences
Provide the following information about your sync preferences to BigPanda:
Required Configuration
Option | Description |
|---|---|
Mode | Determine whether you’d like to set up an incremental or historical sync. Most organizations will need to use both modes. See the Streaming Modes section for more information. |
Optional Pipeline Configuration
Option | Description |
|---|---|
Start Date | If you’re setting up a historical sync, provide the date of when you’d like the sync to begin. If no start date is provided, all data will be synced. We recommend syncing one year of data. |
End Date | Used for historical syncs only. Provide an end date to backfill historical syncs. |
JQL | Additional JQL filter to select which issues will be connected. For example: |
Page size | The number of items requested from JSM in a single call. Default: 50. As JSM makes multiple API calls per issue, this number should be smaller than the page size configured for the Jira data connector. |
Query limit | How many requests can be made to JSM per minute. Default: 20 |