---
title: "Integrations"
description: "Connect TestOrchestrator to Jira, GitHub, Azure DevOps, and more — link test cases, runs, and sessions directly to external issues and tickets."
source: "https://testorchestrator.com/docs/integrations"
---

# Integrations

Integrations connect your test cases, runs, and sessions to issues in external tools — Jira Cloud, GitHub Issues, Azure DevOps, Linear, or a custom tracker. Once configured, team members can link any test object to an external ticket with a single click, and the linked issue’s title and status are fetched from the tracker.

This admin page was called **External references** until September 2026. Links to the old address — in the app or in these docs — redirect here.

> **GitLab Issues is not available.** TestOrchestrator has no GitLab connector yet, so GitLab is not offered when you add a tracker. Every other provider — Jira Cloud, GitHub Issues, Azure DevOps, Notion, Linear and Custom Tracker — has a working implementation.

## How it works

An external reference is a link between a TestOrchestrator object (a test case, run, session, cycle, or result) and an item in an external system. Each link records:

- Which external system the link points to (**Integration Source**)
- The external item's key or URL (e.g., `PROJ-123` in Jira)
- The nature of the relationship (**Relation** — e.g., _Relates to_, _Defect_)

When a source supports reading issue details, TestOrchestrator fetches and caches the issue's current status and assignee so your team can see external issue state without leaving the app.

> **Link from any tracker.** The **Link issue** picker searches every tracker in the project that can be searched (Linear; Jira, GitHub and Azure DevOps with a saved token), and any tracker can be linked by pasting an issue’s link or key. See [Linking issues](https://testorchestrator.com/docs/integrations/linking-issues). Linear also connects with one-click OAuth and adds test-case generation from the Linear sidebar — see the [Linear Integration](https://testorchestrator.com/docs/integrations/linear) guide.

> **Per-connector guides.** Several providers have dedicated pages covering their authentication and AI test-case generation: [Jira](https://testorchestrator.com/docs/integrations/jira), [Azure DevOps](https://testorchestrator.com/docs/integrations/azure-devops), [Linear](https://testorchestrator.com/docs/integrations/linear), and [Notion](https://testorchestrator.com/docs/integrations/notion). GitHub and custom trackers are covered by the generic [Trackers](https://testorchestrator.com/docs/integrations/integration-sources) page.

## Two-part admin setup

Before team members can create external links in their projects, an admin configures two things on the **Trackers** and **Link types** tabs of **Admin → Integrations** (the third tab, **QA agent**, is covered in the [Linear Integration](https://testorchestrator.com/docs/integrations/linear#qa-agent-tab) guide):

1. **Trackers** — one entry per external system instance your organisation uses. Each tracker defines the provider (Jira, GitHub, etc.), how to sign in, what TestOrchestrator can do with it, and which projects can use it. Linear is connected rather than configured.
2. **Link types** — the labels available when creating a link. A link type answers "what kind of link is this?" — for example _Relates to_, _Defect_, or _Blocks_.

Built-in link types exist from the start, so once at least one tracker is set up and enabled, project members with the correct permissions can start linking test objects.

## Example: linking a test case to a Jira defect

1. A tester opens a test case and clicks **Link issue**.
2. They type `PROJ-123` (or paste the issue’s Jira link). The Jira issue appears under its tracker’s logo.
3. They choose _Defect_ under **Link as** and pick the issue.
4. The row appears at once, with the Jira logo on its key. TestOrchestrator fetches the issue’s current status and shows it on the row.

## Who can manage external references?

The Integrations page is available to Tenant Admins and Project Admins with the required permissions. Trackers, link types and linking issues are on every plan, including Free.

The **QA agent** tab is the one part that needs a bigger plan: it comes with **Pro**, and below Pro the tab carries a lock. If the agent was never switched on, the tab shows what Pro adds, with **Upgrade to Pro** for a billing admin or, for everyone else, who can change the plan and an **Ask** button. If it was on before a downgrade, it **pauses**: a banner says so, its approval queue and activity stay readable, and nothing can be approved or switched until the workspace is back on Pro. See [Plans and Billing](https://testorchestrator.com/docs/plans-and-billing).

| Action | Who can access |
| --- | --- |
| View the Integrations admin page | Tenant Admin, Project Admin |
| Create, edit, or delete trackers and link types; manage the QA agent | Tenant Admin, Project Admin |
| Enable or disable sources | Tenant Admin, Project Admin |
| Test an integration connection | Tenant Admin, Project Admin |
| Create, edit, or delete relations | Tenant Admin, Project Admin |
| Enable or disable relations | Tenant Admin, Project Admin |

- [Trackers](https://testorchestrator.com/docs/integrations/integration-sources) — Connect to Jira, GitHub, Azure DevOps, Linear, or a custom tracker — configure auth, capabilities, and project access.
- [Linear Integration](https://testorchestrator.com/docs/integrations/linear) — One-click OAuth, live issue search when linking, AI insight on linked issues, and test-case generation from the Linear sidebar.
- [Linking issues](https://testorchestrator.com/docs/integrations/linking-issues) — Link a case or run to an issue in any tracker — search, paste a link or key, link-only trackers, and Undo on unlink.
- [Jira Integration](https://testorchestrator.com/docs/integrations/jira) — Connect Jira Cloud with email and an API token — reference Jira issues and generate test cases from a Jira issue.
- [Azure DevOps Integration](https://testorchestrator.com/docs/integrations/azure-devops) — Connect with a Personal Access Token — reference Azure Boards work items and generate test cases from a work item.
- [Notion Integration](https://testorchestrator.com/docs/integrations/notion) — Read-only Notion source — reference Notion pages and generate test cases from a spec, PRD, or requirements doc.
- [Link types](https://testorchestrator.com/docs/integrations/relations) — Define the semantic labels for external links — General cross-references or Defect-type relations that appear in defect reporting.
- [MCP Server](https://testorchestrator.com/docs/mcp) — Let an AI client read and write this traceability — link cases to issues, and read coverage gaps — with the `link_to_issue` and coverage tools.
