Jira Changes
The Jira Changes integration notifies BigPanda of any new or updated changes in your Jira Change Management, ensuring these changes are available for use in the RCA process with BigPanda's Root Cause Changes feature.


Supported Versions | Type | Authentication Type |
---|---|---|
Jira Cloud | Native App | API Key and Bearer Token |
Key Features
- Native app to easily integrate BigPanda with Jira.
- JQL filters to target your projects and issues for change management.
- Easy configuration via the configuration form located in the BigPanda Jira app, where you can:
- Map custom statuses in Jira to BigPanda statuses.
- Map custom fields in Jira to BigPanda tags.
- Hide any undesired fields from the BigPanda UI.
How It Works
The BigPanda Jira app creates a Jira webhook that sends BigPanda all new and updated issues matching the customer-provided JQL filter. The change data is processed and normalized according to the configuration provided in the BigPanda Jira app. The prepared change record is then sent to the BigPanda Console.
Data Models
BigPanda converts and organizes Jira issue information into tags.
Default Field Mapping
The table below outlines the default mapping of Jira fields to BigPanda tags. These can be customized in the app configuration.
BigPanda Tag | Jira Field | Description |
---|---|---|
|
| The unique identifier for the change. |
|
| The change status. |
|
| When the change started. |
|
| Summary of the change. |
|
| When the change ended. |
Default Status Mapping
The table below outlines the default mapping of Jira statuses to BigPanda change statuses. These can be customized in the app configuration.
BigPanda Status | Jira Statuses | Description |
---|---|---|
| [none] | A change has been planned but is not yet in progress. |
|
| A change is currently in progress. |
|
| A change was resolved. |
| [none] | A change was cancelled or aborted. |
Managing the Integration
Prerequisites
- Admin access to Jira.
- Create and save a BigPanda API Key.
- Create a Changes REST API integration and save the app key.
Jira Cloud
Installing the Jira App
- Log into your Jira instance.
- In the left panel, go to Jira Settings > Apps > Find new apps.
- Search for and install the BigPanda App.
Setup
- Go to Jira Home.
- Click the BigPanda App from the sidebar.
- Add the API, App key, and JQL Filter.
- Optionally fill out the additional configuration fields.
- Save your changes.
Configuration
Once the BigPanda Jira app is installed, you can configure it by clicking on BigPanda in the main Jira menu.


General Section
The General section allows you to specify the Jira field name for the following BigPanda tags:
start
end
summary
Status Names Section
The Status Names section allows you to specify:
- The Jira field for the change status.
- The mapping of Jira statuses to BigPanda statuses.
Field Format
Provide a comma-separated list of Jira statuses for each BigPanda Status (ie: done, resolved, closed, completed)
Tags Section
By default, all Jira issue fields are mapped to tags in BigPanda using their field names.
Customize Jira field names and BigPanda tag names in the Tags section.
Metadata
BigPanda Changes allows you to hide specific tags from the Console without losing the ability to leverage these tags in correlation. To use the Metadata section to hide specific tags, provide a comma-separated list of the field names you wish to exclude.
Jira Server
Configuring the webhook
A webhook URL needs to be created with all the necessary query parameters to make sure BigPanda processes the Jira Issues correctly.
This table represents all the required and optional query parameters the webhook can leverage.
Query Parameter | Value Options | Description |
---|---|---|
| required BigPanda API Key | |
| required App key for the Change API integration. | |
|
| required Overrides the default status field. |
| Jira field | If |
|
| required Overrides the default status mapping. |
| URI encoded Object Object keys: BigPanda Change statuses See example below | If Reference default status mapping |
| Jira field | Overrides the default |
| Jira field | Overrides the default |
| Jira field | Overrides the default |
| URI encoded Object Object keys: Jira field | This parameter allows you to provide a user friendly name to any Jira field. |
| URI encoded Array Ex: encoded: | This list of Jira fields will hide from the BigPanda Console. |
- Start with the base URL: https://inbound.bigpanda.io/jira/changes
- Add the required query parameters to the URL. Below a basic example of a fully formed URL
https://inbound.bigpanda.io/jira/changes?api_key=1234567890&app_key=0987654321&override_status_field=false&override_status_mapping=false - Add any additional query parameters to meet your desired configuration
URL Encoding
For the
status_mapping
andtags
parameters, it is required to URI encode the values. Here is an example of this encodingSample Status Mapping
{ "Planned": ["approved", "in review"], "In Progress": ["pending"], "Done": ["done", "finished"], "Canceled": ["cancelled", "rejected"] }
URI Encoded Object
%7B%22Planned%22%3A%20%5B%22approved%22%2C%22in%20review%22...Note: All extra spaces must be removed prior to encoding the object
Creating the Webhook
- Log into your Jira instance.
- In the left panel, go to Jira Settings > System > Webhooks.
- Click on Create a Webhook
- Enter a name for the webhook
- Add your generated webhook from the previous step.
- Add a JQL Query to the webhook so that only the projects you want are pushed to BigPanda
- Check the Issue
created
andupdated
checkboxes. - Click create at the bottom.
Uninstalling the Integration
Jira Cloud
- Uninstall the app by navigating to Jira Settings > Apps > Manage apps.
- Use the Uninstall button for the BigPanda App.
Jira Server
- Uninstall the app by navigating to Jira Settings > System > Webhook.
- Select the BigPanda webhook and click on the delete button
Updated 11 months ago