> ## Documentation Index
> Fetch the complete documentation index at: https://docs.traversal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Jira

> Connect Jira for issue tracking and project context during investigations.

Connecting Jira lets Traversal read issues and projects so it can relate incidents to engineering work.

## What Traversal reads

* **Issues**: issue details, status, priority, and assignee via JQL search
* **Comments**: comment threads on issues
* **Attachments**: images and text, JSON, or XML attachments up to 512 KiB

## Atlassian Cloud setup

**1. Create an API token**

1. Open [Atlassian API tokens](https://id.atlassian.com/manage-profile/security/api-tokens) and sign in
2. Create an API token for Jira, give it a descriptive name, and choose an expiration date
3. If Atlassian shows a scoped-token flow in your organization, select the Jira app and grant read-only access. `read:jira-work` covers the Jira endpoints Traversal uses to read issues, comments, JQL search results, and attachments
4. Copy the generated token right away. Atlassian shows it only once

**2. Configure in Traversal**

Go to **Integrations**, select Jira, and enter:

* Jira instance URL (usually your site URL, such as `https://company.atlassian.net`)
* Email address associated with your Atlassian account
* API token
* Cloud ID, only if your Jira URL uses Atlassian's API gateway instead of your site URL

### Jira URL and Cloud ID

Use your Jira site URL, such as `https://company.atlassian.net`, whenever possible.

If your organization routes Jira API traffic through Atlassian's API gateway instead of your site URL, also provide the site's **Cloud ID**. Atlassian's current docs refer to this as `cloudId` in gateway URLs such as `.../ex/jira/{cloudId}/...`, and Traversal exposes a separate `Cloud ID` field for those setups.

## Jira Data Center setup

**1. Choose an account**

Choose a Jira account that can read the projects and issues you want Traversal to access.

**2. Configure in Traversal**

Go to **Integrations**, select Jira, choose **Username & Password**, and enter:

* Full Jira URL, including a context path such as `/jira` when applicable
* Username
* Password

Traversal uses Jira REST API v2 for Jira Data Center. Personal access token, bearer token, and SSO-only authentication aren't supported.

Assets, Jira Service Management ops alerts, and dedicated changelog reconstruction aren't included in Jira Data Center support.

## Private network access

If the service endpoint isn't directly reachable by Traversal (as is common with self-hosted services), deploy a [Traversal Connector](https://docs.traversal.com/architecture/connector.md) in a network that can reach it. When configuring the integration, select that connector under **Network Access Needed**. The service endpoint doesn't need public internet exposure.

See [Set up the Traversal Connector](https://docs.traversal.com/setup/connector.md) for deployment and network requirements.

## More information

* [Atlassian API tokens](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/)
* [Jira scopes for Atlassian scoped tokens](https://developer.atlassian.com/cloud/jira/platform/scopes-for-oauth-2-3LO-and-forge-apps/)
* [Atlassian API gateway and Cloud ID](https://developer.atlassian.com/cloud/oauth/getting-started/making-calls-to-api/)
* [Find your Atlassian Cloud ID](https://support.atlassian.com/jira/kb/retrieve-my-atlassian-sites-cloud-id/)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.