Jira Plugin for Ticket Orchestrator

Jira Plugin for Ticket Orchestrator

This document explains how to configure your Jira v1.1.0 plugin integration with the Ticket Orchestrator module of the Netskope Cloud Exchange platform.


To complete this configuration, you need:

  • A Netskope tenant (or multiple, for example, production and development/test instances) that is already configured in Cloud Exchange.
  • A Netskope Cloud Exchange tenant with the Ticket Orchestrator module already configured.
  • A Jira account.
  • Connectivity to the following host: https://*.atlassian.net

Netskope CE: v4.1.0, v4.2.0

Performance Matrix

This performance reading has been considered after keeping the plugin running for few hours and taking random readings per minute to collect the average count for the number of tickets that are generated in JIRA. The reading are collected on a Large CE Stack with below mentioned specifications.

Stack Details:

Size: Large

RAM: 32 GB

CPU: 16 Cores

Tickets created on third-party product

~ 50 per minute


API Details

The plugin uses the Jira Cloud platform REST API to create an issue, get fields, get all projects, get issues, get create issue metadata, get issue state, update issues, and validate credentials from the Jira platform.

Refer to the official documentation for more information on the Jira Cloud platform REST API


List of APIs Used

API details



Validate authentication



Get the list of Jira projects as queues.



Get a list of all the available fields.



Get issues



Get create issue metadata



Create an issue on the Jira platform



Sync issue state



Update issue on the Jira platform



User Agent

The user agent added for this plugin is in the following format: / which will be:

  • netskope-ce-4.2.0-cto-jira itsm-v1.1.0


  1. Get a Jira API token.
  2. Configure the Jira plugin.
  3. Configure Ticket Orchestrator Business Rules for Jira.
  4. Configure Ticket Orchestrator Queues for Jira.
  5. Validate the Jira Plugin.

Click play to watch a video.


Get a Jira API Token

  1. To create a new Jira Cloud API key, go to https://id.atlassian.com/manage-profile/security/api-tokens and log in using an account with at least following permissions:
  2. Go to Your Profile and Settings and click Profile.
  3. Click Manage your account.
  4. Click Security (tab), and then click Create and manage API tokens.
  5. Click Create API token.
  6. Enter a descriptive Label for your token and click Create.
  7. Click Copy, and then save the token in a secure place for when you configure the Jira plugin. Note that this token is only available when creating a token.
  8. When finished, click Close.

Configure the Jira Plugin

  1. In Cloud Exchange, go to Settings > Plugins.
  2. Search for and select the Jira v1.1.0 plugin box to open the plugin creation page (make sure the Ticket Orchestrator module is enabled. If not, go to Settings > General and enable the Ticket Orchestrator module).
  3. Enter a Configuration Name.
  4. Adjust the Sync Interval to an appropriate value: Suggested is 5+ minutes.
  5. Click Next.
  6. Enter your Jira Cloud URL. This should be in the following format: https://<your-domain>.atlassian.net.
  7. Enter the user email address for the API token.
  8. Enter your API Token.
  9. Click Next.
  10. Enter the comma-separated Jira issue type(s). Note that the values are case-sensitive.
  11. Click Save.

Configure Ticket Orchestrator Business Rules for Jira

Create a business rule based on the filters you need to generate tickets in the JIRA plugin.

  1. Go to Ticket Orchestrator and click Business Rules.
  2. Click Create new rule.
  3. Enter the appropriate Rule Name in the text box and build the appropriate filter query condition on field(s) for the business rule. You can also type the query manually by clicking Filter Query.
  4. Click Save.
  5. To test the newly created business rule, click on the refresh image14.png icon, enter a time period (in days), and click Fetch. This shows the number of alerts that are eligible for incident/ticket creation.

Configure Queues for Jira

  1. Go to Ticket Orchestrator and click Queues.
  2. Click Add Queue Configuration.
  3. Select your previously created Business Rule from the dropdown.
  4. Select the plugin configuration from the dropdown for which the queue is being configured.
  5. Select the Queues from the dropdown. This will list the Jira Projects available on the configured Jira instance. The issues/tickets will be created in the selected project.
  6. Add/Map appropriate values between alerts and incidents under the Map Field section. Alert’s attributes can be accessed via “$” in the custom message field. Click Add to add more field mappings.


    The user must provide the value of the field in its respective schema. For most of the fields, the schema is available here.

  7. Click Save.
  8. Based on the business rule(s), Jira tickets for incoming alerts will be created automatically. To create Jira tickets for historical alerts, click the refresh image14.png button for the configured queue, enter the time period (in days), and then click Fetch. This shows the number of alerts that are eligible for ticket creation. Click Sync to create Jira tickets for those alerts.

Validate the Jira Plugin

In order to validate the workflow, you must have Netskope Alerts.

Validate In Netskope Cloud Exchange

  1. Go to Ticket Orchestrator and click Alerts.
  2. To view the list tickets created on Jira, go to Tickets.
  3. If tickets are not being created on Jira, you can look at the audit logs in Cloud ExchangeIn Cloud Exchange, click Logging and look through the logs for errors.

Validate In Jira

  1. Click on the External Link of any ticket to directly navigate to the newly created Jira ticket.

Troubleshooting the Jira Plugin

Fields are not appearing in Jira.

  1. Go to your Jira project.
  2. Go to Project Settings > Issue > Screens.
  3. Click Create.
  4. Click Select Field and add the field.


There are some common fields that are typically not allowed to be set during the ticket creation via API to ensure data integrity and prevent potential issues.

Common fields that are usually read-only or automatically managed by Jira during a ticket creation. There might be more fields that are set by Jira or not allowed to be set while creating a ticket through APIs.

Below are a few examples of the same:

  • Status
  • Created
  • Updated
  • Issue ID
  • Created Date
  • Updated Date
  • Created By
  • Updated By
  • Key
  • Images
  • Request participants
  • Linked Issues

Netskope also does not support uploading files through CE, which is why the field “Attachment” is not supported.

Share this Doc

Jira Plugin for Ticket Orchestrator

Or copy link

In this topic ...