Skip to content

Integrating SailPoint with Atlassian Cloud Jira Service Management

Integration

This is an integration and requires additional licensing or subscriptions to utilize it. For more information, contact your customer success manager.

Atlassian Cloud Jira Service Management is a software platform that supports IT service management and automates common business processes for requesting and fulfilling service requests across a business enterprise.

The new service desk functionality provides an easy way to:

  • See a list of integrations
  • View summaries of the integrations
  • Create new integrations
  • Edit/Update existing integrations
  • Delete integrations

This guide helps you configure the Service Desk Integration Module. It converts SailPoint provisioning actions into tickets in the Atlassian Cloud Jira Service Management system.

Note

  • You must have an active SailPoint license to use this integration. Contact your Customer Success Manager for more information.
  • The Atlassian Cloud Jira Service Management integration supports only the Service Request and Incident ticket types.
  • All activity on the Service Desk source appears as events in Search and on the Activity tab of an identity. For more information, refer to Using Search - Events.

Note

To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the SaaS Release Notes page.

Supported Features

  • Creation of tickets for manual provisioning operations and status checks.
  • Synchronization of ticket status between SailPoint's Atlassian Cloud Jira Service Management Integration Module and the Atlassian Cloud Jira Service Management system.
  • Retry Mechanism for Check Ticket status failure.

Note

The Atlassian Cloud Jira Service Management Integration can be configured as a SaaS Connection Type for SaaS connectivity that doesn't require a Virtual Appliance Cluster.

Prerequisites

Important

For Service Desk Integration Module to function properly, ensure that the feature flag GOV_DISABLE_PLAN_INITIALIZER is set to true for your organization. For more information, reach out to Professional Services/Expert Services.

  • Configure the virtual appliance cluster only when using a VA-based connection type. For instructions, refer to the Virtual Appliance Reference Guide.

    Note

    This requirement doesn't apply to SaaS connections.

  • Configure at least one source to generate manual tasks for Provisioning. For more information, refer to Configuring Source Account Provisioning.

  • Be familiar with Apache Velocity scripting. For more information, refer to Apache Velocity Engine - Getting Started.

  • Determine the authentication option (Basic or OAuth 2.0) you want to use for your system to authenticate into Atlassian Cloud Jira Service Management system.

Required Permissions

The minimum access permissions required for a user to create and get the status of tickets using the Next-generation Service Desk type project, requires the following permissions to be assigned:

  • User Access:
    • Has access on site
    • Jira Service Management
  • Set Roles type as Basic

The minimum project role and access required for a user to create and get the status of tickets using the Classic Service Desk type project, requires the following permissions to be assigned:

  • Project Role:
    • Service Desk Team
  • User Access:
    • Has access on site
    • Jira Service Management
  • Set Roles type as Basic

Admin user level permissions are required to access the Atlassian Cloud Jira Service Management Integration Module.

System Requirements

  • The Atlassian Cloud Jira Service Management system is deployed in your IT environment.

  • The virtual appliance must be able to connect to the ITSM system when using a VA-based connection type, typically using outbound access for port 443 (HTTPS).

    Note

    This requirement doesn't apply to SaaS connections.

Best Practices

Before you start the configuration process, you should make decisions about the following components of this integration:

  • Identify - Find the Atlassian Cloud Jira Service Management system and the resources that will be used in the connection. Use the Name and Description fields in General Settings to clearly identify the specific Atlassian Cloud Jira Service Management system and the sources used in the connection.
  • Atlassian Cloud Jira Service Management Details - You can create an integration for each Atlassian Cloud Jira Service Management system your company uses. If the integration meets the prerequisites, you need to identify the URL for each instance you want to integrate with. You also need to identify the administrator details and the applicable authentication requirements.

  • Sources - For each source you want to integrate with an Atlassian Cloud Jira Service Management system, verify that it is configured for provisioning. For more information, refer to Prerequisites.

    Tip

    Edit the Description field for these sources to indicate they are used in the Atlassian Cloud Jira Service Management Integration Module.

  • Atlassian Cloud Jira Service Management Statuses - Make a list of each possible status in the Atlassian Cloud Jira Service Management system that you want to map to a status in SailPoint. This will help you track tickets as they're worked. Most importantly, SailPoint uses this mapping to determine when a ticket is closed in the Atlassian Cloud Jira Service Management system so that the related provisioning task is also treated as complete. For more information about mapping statuses, refer to Status Mapping.

  • Requests - Identify each type of provisioning action in SailPoint that you want to create a ticket for in the Atlassian Cloud Jira Service Management system, along with the information from those actions that should be included in the related Atlassian Cloud Jira Service Management system ticket. For more information, refer to Ticket Creation.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.