# Jira Service Management

<!-- BEGIN GENERATED:intro -->

The Jira Service Management connector is a [Palantir-provided driver](../../data-integration/foundry-provided-drivers/index.md) for Jira Service Management.

To create a new Jira Service Management source, follow the [standard setup flow for Palantir-provided drivers](../../data-integration/foundry-provided-drivers/index.md#setup), then use the sections below for Jira Service Management-specific configuration and networking. For the complete property reference, see the [official Jira Service Management driver documentation ↗](https://cdn.cdata.com/help/GKM/jdbc/pg_connectionj.htm).

<!-- END GENERATED:intro -->

<!-- BEGIN GENERATED:capabilities -->

:::callout{theme="neutral" title="Beta"}
The Jira Service Management connector is in the [beta](../../platform-overview/development-life-cycle/index.md) phase of development and may not be available on your enrollment. Functionality may change during active development.
:::

## Supported capabilities

| Capability | Status |
|---|---|
| Exploration | 🟡 Beta |
| Batch syncs | 🟡 Beta |
| Incremental | 🟡 Beta |
| [OAuth 2.0 authentication](#oauth-20-authentication) | 🟡 Beta |
| [Table exports](#table-exports) | 🟡 Beta |

<!-- END GENERATED:capabilities -->

<!-- BEGIN GENERATED:configuration -->

## Configuration

The properties below are mandatory or recommended.

| Property | Required? | Description | Default |
|---|---|---|---|
| [`AuthScheme` ↗](https://cdn.cdata.com/help/GKM/jdbc/RSBJiraServiceDesk_p_AuthScheme.htm) | Mandatory | The type of authentication to use when connecting to Jira Service Management. | `APIToken` |
| [`URL` ↗](https://cdn.cdata.com/help/GKM/jdbc/RSBJiraServiceDesk_p_URL.htm) | Mandatory | The URL to your JIRA Service Management endpoint. | `https://yoursitename.atlassian.net` |
| [`APIToken` ↗](https://cdn.cdata.com/help/GKM/jdbc/RSBJiraServiceDesk_p_APIToken.htm) | Recommended | APIToken of the currently authenticated user. | — |
| [`InitiateOAuth` ↗](https://cdn.cdata.com/help/GKM/jdbc/RSBJiraServiceDesk_p_InitiateOAuth.htm) | Recommended | Specifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working. | `REFRESH` |
| [`OAuthClientId` ↗](https://cdn.cdata.com/help/GKM/jdbc/RSBJiraServiceDesk_p_OAuthClientId.htm) | Recommended | Specifies the client ID (also known as the consumer key) assigned to your custom OAuth application. This ID is required to identify the application to the OAuth authorization server during authentication. | — |
| [`OAuthClientSecret` ↗](https://cdn.cdata.com/help/GKM/jdbc/RSBJiraServiceDesk_p_OAuthClientSecret.htm) | Recommended | Specifies the client secret assigned to your custom OAuth application. This confidential value is used to authenticate the application to the OAuth authorization server. | — |
| [`User` ↗](https://cdn.cdata.com/help/GKM/jdbc/RSBJiraServiceDesk_p_User.htm) | Recommended | Specifies the user ID of the authenticating Jira Service Management user account. | — |

<!-- END GENERATED:configuration -->

<!-- BEGIN GENERATED:networking -->

## Networking

The table below lists the domains that the source must be able to access to run.

For each domain, add a corresponding [egress policy](../../administration/configure-egress/index.md). If the source is hosted on-premises and not directly reachable from Foundry, use an [agent proxy egress policy](../../administration/configure-egress/index.md#agent-proxy-egress-policies) instead. The agent host itself must also be able to reach the listed domains. See [using an agent as a proxy](../../data-connection/agent-proxy/index.md) for details.

| Domain  | Required |
|--- |--- |
| \<URL> | URL connection property (usually https://yoursitename.atlassian.net) |
| api.atlassian.com | If `AuthScheme=OAuth` |
| \<SSOLoginURL> | If `AuthScheme=Okta` or Crowd |
| \<SSOExchangeURL> | If `AuthScheme=Okta` or Crowd |

<!-- END GENERATED:networking -->

<!-- BEGIN GENERATED:oauth -->

## OAuth 2.0 authentication

This connector supports OAuth 2.0 authentication. Follow the [OAuth 2.0 guidance for Palantir-provided drivers](../../data-integration/foundry-provided-drivers/index.md#oauth-20-authentication) to configure and authorize the connection.

<!-- END GENERATED:oauth -->

<!-- BEGIN GENERATED:table-exports -->

## Table exports

This connector supports table exports. Learn how to [set up a table export](../../data-connection/export-overview/index.md#table-exports).

<!-- END GENERATED:table-exports -->