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

# Jira

> Let the QA.tech agent read Jira issues for PR reviews and test planning

Connect **Jira Cloud** to QA.tech so agents can **read** issues from your configured project — titles, descriptions, acceptance criteria, status, and more. That context powers smarter testing during [PR reviews](/configuration/github-app) and when you plan tests in the [AI Chat Assistant](/core-concepts/ai-chat-assistant).

QA.tech does **not** sync Jira in the background. Issues are fetched on demand when an agent or chat request needs them. You can also create Jira tickets from chat, or manually export a detected test issue (legacy workflow).

<Note>
  **Requirements:** Jira **Cloud** only (Atlassian OAuth). Self-hosted Jira
  Server or Data Center is not supported. Connect at the organization level,
  then pick a Jira project and issue type in project settings.
</Note>

## What the Agent Reads from Jira

Reads are scoped to the **Jira project you configure** in project settings. QA.tech uses your OAuth connection to call the Jira Cloud API on your behalf.

### Issue fields

For each issue the agent fetches or searches, QA.tech reads: **Key**, **Title** (summary), **Description**, **Status**, **Assignee**, **Priority**, **Issue type**, **Labels**, and **URL**.

### Search behavior

The agent uses **plain-text keywords** — not raw JQL. You ask in natural language; QA.tech builds the query.

| You ask for…     | What QA.tech does                                                |
| ---------------- | ---------------------------------------------------------------- |
| A specific key   | Fetches that issue directly (e.g. `PROJ-108`)                    |
| Keyword search   | Searches issue text for your keywords in the configured project  |
| Recent issues    | Returns up to **25** most recently updated issues in the project |
| Issues of a type | Filters by issue type name: `Bug`, `Story`, `Epic`, `Task`, etc. |

Keyword search matches text in issues — it does **not** filter by status (e.g. "open" vs "done"). If you need a specific ticket, ask by key (`PROJ-108`) or describe the topic.

<Note>
  QA.tech does not read boards, sprints, release versions, epics as hierarchy,
  custom fields, attachments, comments, or user directories. It cannot
  automatically list "all stories in release 2.4" from Jira metadata.
</Note>

## How Agents Use Jira Data

### PR and merge request reviews (automatic)

When [GitHub PR review](/configuration/github-app) or [GitLab MR review](/configuration/gitlab) runs, the review agent looks for Jira keys in the PR/MR title, branch name, or commits (e.g. `PROJ-456`).

If a key is found and Jira is connected, the agent **fetches that ticket** and uses the description and acceptance criteria to:

* Understand what the change is meant to do
* Select relevant existing tests
* Create focused tests for gaps
* Scope the review to user-facing behavior described in the ticket

The agent does not create or update Jira issues during review.

> **Example:** A PR titled `PROJ-789 Add coupon field to checkout` triggers a fetch of `PROJ-789`. The agent reads the story description, runs checkout tests, and verifies the coupon behavior matches the ticket.

### Chat-assisted test planning (on demand)

In the [AI Chat Assistant](/core-concepts/ai-chat-assistant), you can ask the agent to pull Jira context before creating or running tests:

> "Pull up PROJ-108 and generate tests based on its acceptance criteria"

> "Find Jira stories about checkout and suggest tests based on their descriptions"

> "List recent bugs in Jira — I want to add regression tests for the top two"

> "Fetch PROJ-201, PROJ-202, and PROJ-203 — then start a release check for those changes"

The assistant returns issue details (including status) you can use to author tests, run existing tests, or describe intended changes for a release check in chat. You provide the ticket keys or search terms — QA.tech does not auto-discover release contents from Jira versions or sprints.

### Creating issues in Jira

The chat assistant can also **create** standalone Jira tickets (summary, description, `qatech` label) in your configured project. It does not update existing issues.

## Setup

<Steps>
  <Step title="Connect to Jira">
    Go to **Settings → Integrations** in your project settings. Click **Manage
    Connections**, then connect Jira. Complete the Atlassian OAuth flow.
  </Step>

  <Step title="Configure the project">
    Return to **Settings → Integrations** and open Jira. Select the **Jira
    project** and **issue type** for agent reads and creates, then click **Save
    Jira Integration**.
  </Step>

  <Step title="Verify (optional)">
    Use **Create Test Issue** after saving to confirm the connection works.
  </Step>
</Steps>

## Jira and Linear Together

If both [Linear](/integrations/linear) and Jira are connected, mention which tracker you want:

> "Search **Jira** for checkout bugs"

If you do not specify, the assistant defaults to **Linear** when both are configured.

## Exporting Detected Issues

QA.tech can also push a [detected test issue](/core-concepts/issues) to Jira manually — one ticket per issue, with test steps and evidence. This is a separate workflow from agent reads; most teams use Jira → QA.tech (read for testing) rather than QA.tech → Jira (export failures).

From the **Issues** page, click **Create ticket**, or from a test run choose **Send to Jira**. Exported tickets include a `qatech` label and a link back to QA.tech.

## Limitations

| Supported                               | Not supported                                       |
| --------------------------------------- | --------------------------------------------------- |
| Read issues in configured project       | Read across all projects in your site               |
| Fetch by issue key                      | Pass raw JQL in chat                                |
| Keyword and issue-type search           | Filter by status, sprint, board, or release version |
| PR/MR review fetches linked ticket keys | Auto-list stories in a Jira release or sprint       |
| Chat fetch/search on demand             | Background sync or webhooks                         |
| Create issues (chat + manual export)    | Update, comment, or transition issues               |
| Jira Cloud (OAuth)                      | Jira Server / Data Center                           |

## Related

* [AI Chat Assistant](/core-concepts/ai-chat-assistant) — search and create tracker issues from chat
* [GitHub App for PR Reviews](/configuration/github-app) — automatic PR testing with linked ticket lookup
* [GitLab MR Reviews](/configuration/gitlab) — same pattern for GitLab
* [Issues](/core-concepts/issues) — detected test issues and manual export
* [Linear](/integrations/linear) — alternative issue tracker integration