Jira Ticketing

Jira integration lets Sysdig users open Jira tickets within the Sysdig Secure UI and assign them to team members directly. The first iteration allows users to open tickets from the CIEM/Identity recommendations from the Home page, after an Administrator has configured the integration.

Currently, you can open are Bug, Story, and Task Jira issue types.

Configure Jira Ticketing Integration

Prerequisites

  • The API token must be created by the same User you input when creating a new Jira Ticketing Integration.
  • The best practice is to set up the integration with a service account email rather than an individual’s email.

Required Permissions

The Administrator with the Jira API token who is setting up the integration must have the following:

  • Permission to access Jira.
  • Administer Jira global permissions, or at least:
    • Permissions to create issues in the Jira project associated with Sysdig.
    • Permissions to create attachments in the Jira project associated with issues coming from Sysdig.

The Sysdig user who will create tickets in the UI must have one of the following:

  • Administer Jira global permission
  • Browse Projects permission for the Jira project associated with Sysdig.
  • Administer Projects permission for the Jira project associated with Sysdig.

Set Up the Integration

  1. Log in to Sysdig Secure as an administrator and open Settings > Ticketing Integrations.

  2. Select Jira.

    The Connect Jira Account window appears.

  3. Specify the following:

    • Integration Name: A relevant name for the integration.
    • Atlassian Cloud URL: Your Jira account URL. For example, https://myacount.atlassian.net.
    • Email: The email address of the API token holder, which matches the email used in the Jira Cloud account.
    • API Token: The Jira token you have generated.

  4. Click Save.

    The Jira integration will be listed on the Ticketing Integrations page with Active status.

Test the Integration

To use the integration, open the Sysdig Secure Home page and check an Identity recommendations, as described [Open JIRA Tickets from Identity Recommendations.