Skip to main content

Netskope Help

Jira Plugin for Ticket Orchestrator

This document explains how to configure your Jira 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)

  • A Netskope Cloud Exchange tenant with the Ticket Orchestrator module already configured.

  • A Jira account.

  1. Create a Jira 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.

  1. To create a new Jira Cloud API key, go to and log in using an account with at least following permissions:

  2. Click Create API token.

  3. Enter a descriptive Label for your token and click Create.

  4. 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.

  5. When finished, click Close.

  1. In Cloud Exchange, go to Settings > Plugins.

  2. Search for and select the Jira 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>

  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.

  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 create Mute Rule(s) and/or Deduplication Rule(s) for this business rule, click on the Business Rule you created.

  6. Click on the round “+” icon to create a new Mute Rule/Deduplication Rule.

  7. Enter a rule name and build the appropriate condition.

  8. Click Save.

  9. Similarly, Deduplication Rule(s) can be created.

  10. 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.

  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.

  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.


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

  1. Go to Ticket Orchestrator and click Alerts.

  2. To view the list tickets created on Jira, go to Tickets.

  3. Click on the External Link of any ticket to directly go to the newly created Jira ticket.

  4. If tickets are not being created on Jira, you can look at the audit logs in Cloud Exchange In Cloud Exchange, click Logging and look through the logs for errors.