Jira Issues - Cloud

In Jira Software Cloud, issues help you manage code, estimate workload, and keep track of your team.

Supported VersionsTypeAuthentication Type
JIRA Cloud <= 9.4Native AppAPI Key and Bearer Token

The BigPanda for Jira integration allows you to automatically create actionable Jira Issues based on high-level correlated BigPanda incidents. Jira issues are synchronized with the corresponding BigPanda alerts allowing you to continue working in Jira while benefiting from BigPanda’s tools. The integration allows you to configure parameters in Jira for the customization of each project instance.

When a BigPanda incident is shared through the Jira integration, a corresponding issue is created in Jira with details of the correlated alerts and links to the BigPanda incident. Changes occurring to the BigPanda Incident will update the corresponding Jira issue. Additionally, if changes occur to the Jira issue, then it updates the corresponding BigPanda.

Classic Software Projects

Currently, only classic software projects are supported with the BigPanda Plugin. If a Next-Gen Project is configured, the plugin will not successfully create a Jira Issue.

Key Features

  • Bidirectional Logic: Configurable settings that allow resolve events for BigPanda incidents to automatically resolve a Jira issue. In addition, you can enable that incidents reopened in BigPanda can reopen a Jira issue.
  • Priority synchronization: Priority levels set for BigPanda incidents can automatically set the priority levels of corresponding Jira Issues.
  • Direct link to BigPanda incident: Links directly from the Jira issue to the BigPanda incident allowing you to view the incident details, the incident preview page, and the incident timeline. You can also view the alerts and changes occurring in the BigPanda console.
  • Field Mapping: Align certain BigPanda alert tags to the fields used by your project's issue type, whether required or optional.
  • Multi-integration: Allows you to set up an integration for each of your Jira projects.

Jira Sync and AutoShare

The JIRA integration follows standard AutoShare rules for outbound shares.

The bi-directional sync is time based, and is in addition to the outbound sharing updates. Changes in either BigPanda or Jira are synchronized within the other platform. By default, information is updated every 15 seconds reducing latency synchronization to less than 5 minutes. As a result, you are provided with an up-to-date view of incidents at real-time.

See Manage AutoShare for more information.

Install the Integration

Administrators can install the integration by following the on-screen instructions in BigPanda.

Configure the Integration in Jira

The BigPanda App makes it easy to configure new projects and customize them to the desired specifications. This is achieved by providing a simple form that is used to set the behavior of the integration and the bi-directional logic.

These are the steps to set up an integration for a new project:

  1. In the Projects section, select Add Project. The Project Configuration dialog box appears.
  2. Configure the Project Configuration settings.
972972

Project Configuration Dialog Box

The dialog box streamlines the process of setting up an integration by automatically providing the list of Jira projects available for integration and setup.

  1. Configure the project and issue parameters:
Parameter NameDescription
BigPanda App KeyApp Key provided by the on-screen instructions in BigPanda for this integration
Jira ProjectSelect the project you want to create the integration for. All your Jira projects are listed here.
Jira Issue TypeSelect an issue type for your project from the drop-down menu:
Ex: Story, Bug, Epic...
  1. Configure the Bi-Directional Logic for closing and re-opening incidents and issues parameters for a specific project:
Parameter NameAction
Auto Resolve BigPanda IncidentEnable this toggle to automatically resolve a BigPanda incident when a corresponding Jira issue marked as done or resolved.
Auto Resolve Jira IssuesEnable this toggle to automatically resolve a Jira issue when a corresponding Bigpanda incident is resolved.
Auto Re-Open Jira IssuesEnable this toggle to reopen a Jira issue when a corresponding BigPanda incident is reopened. Disable if you want to create a new Jira issue when the corresponding BigPanda incident is reopened.
Re-Open Window (min)If you enabled the Re-Open Jira Issues, you can set the timeframe during which the Jira issue can be reopened. If this time frame has passed, then a new Jira issue is created.

The BigPanda Jira App automatically fetches all the statuses defined in your workflow for that project and provides them in a drop-down menu that you can use to set the behavior of the creation, resolve and re-open logic within Jira.

  1. Specify the initial status of a Jira Issue based on various BigPanda actions, by configuring the Status Mapping parameters:
Parameter NameAction
Create Jira Issue as..When a new issue is created by BigPanda it will be opened in this status.
Resolve Jira Issue as...When an incident is resolved in BigPanda and the logic is enabled in the configuration, then the issue will be moved to this status.
Re-open Jira Issue as...When an incident is re-opened in BigPanda and the logic is enabled in the configuration, it will move the Jira issue from the resolution status to this new status.
  1. Configure the Priority Mapping settings for each priority level.

If a priority is defined for a BigPanda incident, you can synchronize it with the Jira issue priority. If there is no priority tag for a BigPanda incident, you can set your own default priority. You can rename the list of priorities to suit the needs of your organization. For example, you can rename P1, P2, P3, P4, and P5 as Critical, High, High, Medium, and Low.

📘

Issue Types and Statuses Can Differ between Projects.

After selecting a project, the Issue types, statuses and priorities are dynamic and are based on the available parameters in the drop-down menu for that project.

🚧

Reconfigure Priority Mapping in Jira for Updates in BigPanda's Priority Tags

For updates done in BigPanda to the Priority Tags, you will need to reconfigure the Priority Mapping in the Jira Project for these updates to take effect.

  1. In Field Mapping, define the BigPanda Incident Tags that will map to different required or optional fields for a specific Project/Issue Type. The user setting up the integration will have to specify the data type that these fields within JIRA hold: (Boolean, Integer, String, Array of Strings, or Array of Integers). This feature requires the configuration of Incident tags in BigPanda.

  2. In Issue Summary, define a description template for a Jira issue. By default, BigPanda provides the following template:

h2. {{priority}} | {{status}}
*Environment:* {{env_name}} {{env_id}}

[Incident Link|{{incident_link}}]

----

h2. {{active_alert_count}} Active Alert(s) ({{alert_count}} Total)
(x) {{critical_count}} Critical | (!) {{warning_count}} Warning | (/) {{ok_count}} Resolved
                                                                   
{{alerts_table}}                                                                   

However, you can customize the way the BigPanda incident information is presented in the Jira issue by using the Jira Markup Syntax (For more information click here and using the provided parameterized fields:

Jira Description FieldDescription
{{priority}}Priority tag from BigPanda
{{status}}The incidents
{{start_time}}Time of when the incident started in BigPanda
{{incident_link}}Link that points back to the incident in BigPanda
{{env_name}}The name of the environment from BigPanda
See Environments
{{env_id}}The id of the environment
{{alert_count}}Total number of alerts in the incident in BigPanda
{{active_alert_count}}Number of alerts either in a critical or warning state in the incident in BigPanda
{{critical_count}}Number of critical alerts in the BigPanda incident
{{warning_count}}Number of warning alerts in the BigPanda incident
{{ok_count}}Number of resolved alerts in the BigPanda incident
{{acknowledged_count}}Number of acknowledged alerts in the BigPanda incident
{{unknown_count}}Number of unknown alerts in the BigPanda incident
{{alerts_table}}The list of alerts from the BigPanda Incident
  1. Select Save. After setting your configurations, the shared BigPanda incidents that created Jira Issues are displayed on the task board according to the configurations you made.

View the Jira Issue Workflow

  1. Select the Jira Issue from the list of your projects. The Issue Glance dialog box opens. The issue summary appears in the description field in the left pane. The issue glance appears in the right pane. The glance provides a quick overview of information relating to an issue, including the BigPanda incident and its priority status.
786786

Example of a Jira Issue

  1. To change the configurations, set the following parameters:
ParameterDescription
DescriptionConfigure the description template based on the Issue Summary.
Issue StatusSelect the issue status from the drop-down menu.
PrioritySelect the issue priority from the drop-down menu.
Field MappingSelect the field mapping from the drop-down menus.
  1. To link to the BigPanda console, select the BigPanda Incident.

  2. Select Correlated Alerts. The Alerts tab displays a table of all BigPanda alerts associated with the Jira Issue, including the alert status and its primary and secondary properties.

  3. Select Related Changes. The Changes tab displays any changes determined to be suspect or match changes for the associated alert. A suspect change indicates a change that may be related to the current alert. A match change indicates a change determined to be related to the current alert. The table remains empty if no suspect or match changes related to the alert are found.

  4. For extra details, select any of the following links:

ParameterDescription
View TimelineDisplays the incident timeline in BigPanda.
Incident PreviewDisplays the incident preview page where you can see the latest incident status without logging in to BigPanda.
View IncidentLinks directly to the incident feed and displays the highlighted incident and the incident overview.

Uninstall the Integration

Deleting an integration requires changes to both the integrated system and BigPanda. You must uninstall the integration on the integrated system and then delete the integration from BigPanda.

🚧

When replacing an existing integration with a new tool or system, we recommend configuring the new integration first to ensure no data is lost.

Stop Sending Data from BigPanda

In BigPanda, disable any settings that send data to the integrated system. This includes modifying or removing AutoShare rules or Environments that are tied to the integration.

Stop Sending Data to BigPanda

Disable any settings that send data to BigPanda.

Jira Cloud

  1. Uninstall the app by navigating to Jira Settings > Apps > Manage apps.
  2. Use the Uninstall button for the BigPanda App.