Setting up Jira Integration in SOAR to sync case data between SOAR, JIRA, and Resolution Intelligence Cloud

  • Updated
Table of Contents:

Overview

The SOAR to Jira integration enables sync of cases created in Chronicle SOAR for ActOns generated in the Resolution Intelligence Cloud (RIC) with Jira. This integration ensures that cases are consistently reflected across all platforms, maintaining data accuracy and synchronization.

Once the integration is set up, you can automatically sync comments and closure statuses between Jira, SOAR, and RIC. For instance:

  • Comment Sync: Any comment added on one platform is automatically reflected across SOAR, Jira, and RIC.
  • Ticket Closure Sync: Closing a ticket on one platform (SOAR, Jira, or RIC) triggers the same closure status to be updated across all platforms.

This integration ensures a consistent workflow, with updates flowing smoothly between Jira, SOAR, and RIC in a three-way synchronization.

Integration Steps

  1. Install Jira app in SOAR
    • First, you need to install the Jira app in SOAR.
  2. Import Scripts for Syncing Tickets
    • Import the necessary scripts to establish a connection between SOAR, Jira, and Resolution Intelligence Cloud for data exchange.
  3. Create a Playbook for Ticket Sync
    • Create a playbook to sync tickets between SOAR and Jira based on defined conditions. The playbook is a workflow that triggers specific tasks based on defined conditions. For this integration, two tasks are created: the first task generates Jira tickets for SOAR cases when the conditions are met, while the second task ensures that any updates to the ticket—such as comments or closure status changes—are reflected in the corresponding SOAR case.
  4. Set Up a Job for Syncing Comments and Closures
    • Create a job that automatically syncs comments and ticket closure statuses between SOAR and Jira at the set frequency.

User Roles

To integrate SOAR with Jira, you must have the following role:

  • Admin

Prerequisites

  • Ensure you have an active Jira account with admin privileges.
  • A valid Chronicle SOAR instance with access credentials.
  • Obtain API keys from Jira for integration.
  • Create a custom field in Jira to store the case ID. To create a custom field in Jira, see Setting Up a Custom field (ri_acton_id) in Jira.

Integrating SOAR with Jira

Use this procedure to integrate SOAR with Jira.

  1. Log in to your Chronicle SOAR instance using valid credentials.
  2. From the Home page, click the marketplace icon at the top right corner.
  3. Search for "Jira Integration" in the search bar.
  4. Click the Install button below the app. The Jira Integration app will be installed in your Chronicle instance.
    • To enable it to work with Resolution Intelligence Cloud, contact Resolution Intelligence Cloud support to obtain the additional script files.
    • Add the script files to SOAR using the Import Packages option.
  5. Complete the integration setup in the shared instance by providing the following details:
      1. Environment: By default, this is set to the shared instance.
      2. Instance Name: Enter the name of the instance.
      3. Description: Provide a description for the instance.
      4. In the Parameters section, specify the following information:
        1. API Root: Enter the URL to access the JIRA app.
        2. Username: Provide the username for JIRA account access.
        3. API Token: Enter the API key for JIRA account access.
  6. Click Save to create the instance.

7. Configure Create Jira Issue and Update Issue Id actions in the playbook.

8. In the Jobs Scheduler page of SOAR, configure the Sync Comments job to set the frequency at which it should run, ensuring comments are automatically synced between SOAR and Jira.

  • API Root : The base URL of the Jira Instance
  • Username : The username of the account Configured
  • Project Key: The name of the Jira project in which the tickets must be created.
  • Days Backwards : Specifies the duration of the search space of project keys
  • SOAR Comment Prefix: Specifies the prefix of all comments synced from SOAR
  • Jira Comment Prefix: Specifies the prefix of all comments synced from Jira
  • SOAR Case ID Field: Specifies the Jira custom field number configured in Jira to store the Case Id received from SOAR.
  • API TOKEN: Specifies the API token key of the configured Jira user

9. In the Jobs Scheduler page of SOAR, configure the Sync Closures job to set the frequency at which it should run, ensuring the closure status of cases is automatically synced between SOAR and Jira.

  • API Root : The base URL of the Jira Instance
  • Username : The username of the account Configured
  • Project Key : Specifies the name of the project configured
  • Days Backwards : Specifies the duration of the search space of project keys
  • SOAR Case ID Field: Specifies the Jira custom field number you want to store the Case ID of SOAR
  • Jira Configured Close Status : Specifies the configured name of closed status in the Jira instance
  • API TOKEN : Specifies the API token key of the configured Jira user

By completing the integration setup, cases in SOAR are created as tickets in JIRA when the conditions in the playbook are met. Updates to the tickets, including comments and closure statuses, will be reflected across all integrated platforms (Resolution Intelligence Cloud, SOAR and JIRA). 

Related articles

Comments

0 comments

Please sign in to leave a comment.