Skip to main content
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 and when you plan tests in the 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).
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.

​
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. 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.
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.

​
How Agents Use Jira Data

​
PR and merge request reviews (automatic)

When GitHub PR review or GitLab MR review 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, 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 suggest tests for those changes”
The assistant returns issue details (including status) you can use to author tests or run existing tests. 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

1

Connect to Jira

Go to Settings → Integrations → Jira. Connect Jira and complete the Atlassian OAuth flow. The Jira account is shared by every project in the organization.
2

Configure the project

On the same page, select the Jira project and issue type for agent reads and creates, then click Save Jira Integration.
3

Verify (optional)

Use Create Test Issue after saving to confirm the connection works.

​
Jira and Linear Together

If both 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 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). On an issue page, click Create ticket, or from a test run choose Send to Jira. There is no project issues list in the sidebar. Exported tickets include a qatech label and a link back to QA.tech.

​
Limitations