---
title: "Jira Integration"
description: "Connect TestOrchestrator to Jira Cloud with an email and API token — reference Jira issues from test objects and generate test cases from a Jira issue."
source: "https://testorchestrator.com/docs/integrations/jira"
---

# Jira Integration

Jira Cloud is a built-in integration source in TestOrchestrator. Once an administrator connects your Jira site, your team can reference a Jira issue from a test case, run, or exploration, and point the AI test-case generator at a Jira issue to draft cases that map to your project's template.

> Jira is a built-in [integration source](https://testorchestrator.com/docs/integrations/integration-sources). Everything about [relations](https://testorchestrator.com/docs/integrations/relations), project scope, and where links appear is shared with all other sources — this page covers what is specific to Jira.

## Connecting Jira in Settings

Jira is configured like any other source in **Admin → Integrations → Trackers**. The shared mechanics — the SOURCE, CAPABILITIES, and PROJECTS tabs, testing the connection, and enabling or disabling the source — are covered in [Trackers](https://testorchestrator.com/docs/integrations/integration-sources). The steps below cover what is specific to Jira Cloud.

1. In Jira, generate an **Atlassian API token** for the account TestOrchestrator should authenticate as.
2. In TestOrchestrator, open **Admin → Integrations → Trackers** and click **Create a source**. Choose **Jira Cloud** as the provider.
3. Set the **Base URL** to your Jira site, for example `https://yourcompany.atlassian.net`.
4. For authentication, supply your Atlassian account **email plus the API token** as the credential.
5. **Test** the connection to confirm TestOrchestrator can reach Jira, then assign the source to **all projects** or to **specific projects** on the PROJECTS tab.

## Linking a Jira issue

Once the Jira source is enabled for a project, members with permission to manage external references can link a Jira issue to a test case, run, or exploration.

1. On a test case or run, click **Link issue**.
2. Type words from the issue or its key (e.g., `PROJ-123`) — Jira is searched along with the project’s other trackers — or paste the issue’s link.
3. On a test case, choose the [link type](https://testorchestrator.com/docs/integrations/relations) under **Link as**, then pick the issue.

Search needs a saved API token. The search covers every Jira project the token’s account can see. Without a token, Jira is _link only_: paste the issue’s link or key and the row shows _No details_. See [Linking issues](https://testorchestrator.com/docs/integrations/linking-issues) for the picker, the tracker chips and what each tracker can do.

## Generating test cases from a Jira issue

Point the AI test-case generator at a Jira issue to draft test cases that map to your project's template. Generation is initiated from inside TestOrchestrator. The drafted cases are created in the project you generate them into and can be reviewed and edited like any other test case.

> Test-case generation from a Jira issue is an AI-assisted feature and is available on plans that include AI capabilities. Generated cases are drafts — always review them against the source issue before relying on them.

## Who can do what

| Action | Who can do it |
| --- | --- |
| Create, test, or disable the Jira source; assign projects | Admins with access to the Integrations admin page |
| Link a Jira issue to a test object | Project members with permission to manage external references |
| Generate test cases from a Jira issue | Project members with permission to generate test cases (AI plans only) |

## Related

- [Trackers](https://testorchestrator.com/docs/integrations/integration-sources) — How sources are configured, the authentication types available, capabilities, and project scope.
- [Link types](https://testorchestrator.com/docs/integrations/relations) — Define the semantic labels — General or Defect — applied to every external link.
