Skip to main content
Connecting Jira allows Traversal to access issues and projects, enabling correlation of incidents with engineering work.

​
What Traversal reads

  • Issues — issue details, status, priority, and assignee via JQL search
  • Comments — full 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 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 only shows it once
2

Configure in Traversal

Go to Company Knowledge > 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 Company Knowledge > 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 are not supported. Assets, Jira Service Management ops alerts, and dedicated changelog reconstruction are not included in Jira Data Center support.

​
Private network access

If the service endpoint is not directly reachable by Traversal (as is common with self-hosted services), deploy a Traversal Connector in a network that can reach it. When configuring the integration, select that connector under Network Access Needed. The service endpoint does not need public internet exposure. See Set up the Traversal Connector for deployment and network requirements.

​
More information