Jira Service Management Connector¶

Summary¶

The Jitterbit Harmony Jira Service Management Connector establishes access to Jira Service Management.

The Jira Service Management connector provides an interface for creating a Jira Service Management connection, the foundation used for generating instances of Jira Service Management activities. Activities interact with Jira Service Management through the connection and are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

The Jira Service Management connector is accessed from the design component palette's Connections tab (see Design Component Palette).

The connector works with both Jira Service Desk Cloud accounts and Jira Service Desk Server instances.

Atlassian Jira Service Management was formerly known as Jira Service Desk and received its new name as of its version 4.14. However, there are many references to Service Desk in this documentation, the Atlassian documentation, and the Atlassian REST APIs. See the Atlassian Service Management 4.14.x release notes for details.

Connection Documentation¶

See Jitterbit's comprehensive Jira Service Management connection documentation, which is provided at a dedicated website. Configuration details such as these are included:

• Getting Started: Initial steps for establishing a connection.
• Advanced Features: User-defined views and SSL configuration.
• Data Model: The data model that the connector uses to represent the endpoint.
• Advanced Configurations Properties: Properties that can be defined to configure the connection for both basic and advanced configurations.

Activity Documentation¶

Together, a specific Jira Service Management connection and its activities are referred to as a Jira Service Management endpoint:

• Query: Retrieves records from a table at Jira Service Management and is intended to be used as a source in an operation. (Generically documented in Query Activities.)

• Create: Inserts a record into a table at Jira Service Management and is intended to be used as a target in an operation. (Generically documented in Create Activities.)

• Update: Updates a record in a table at Jira Service Management and is intended to be used as a target in an operation. (Generically documented in Update Activities.)

• Delete: Deletes a record from a table at Jira Service Management and is intended to be used as a target in an operation. (Generically documented in Delete Activities.)

Prerequisites and Supported API Versions¶

The Jira Service Management connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.

This connector requires the use of a Private Agent.

Refer to the Atlassian documentation for information on the schema nodes and fields.

OAuth Authentication¶

OAuth authentication is supported as described in Connections under Configure OAuth Connections.

Troubleshooting¶

If you experience issues with the Jira Service Management connector, these troubleshooting steps are recommended:

1. Ensure the Jira Service Management connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.

2. Check the operation logs for any information written during execution of the operation.

3. Enable operation debug logging for Private Agents to generate additional log files and data.

4. Enable connector verbose logging for this connector using this specific configuration entry of logger name and level:

   <logger name="org.jitterbit.connector.verbose.logging.JiraServiceDesk" level="TRACE"/>
   

5. Check the agent logs for more information.