Where results land

Jira integration

TesterArmy turns the issues the agents find into Jira tickets through one connection shared by the whole project.

START TESTING FOR FREE READ THE SETUP DOCS

[01] Ticket

What the ticket carries

Each Jira ticket includes the issue's description, expected versus actual behavior, reproduction steps, a priority mapped from severity, a screenshot link and a link back to the TesterArmy issue.

Jira · QA-42

Discount code is not applied at checkoutSeverity 5QA-42

Priority: Highest
Description: The code field accepts the value but the order total does not change.
Expected vs actual: The total should drop by the discount but stays at the full price.
Reproduction steps: Sign in, add an item, open checkout, enter the code, press Apply.
Screenshot: View screenshot
TesterArmy issue: Open in TesterArmy

One connection
One teammate connects an Atlassian account and the connection is shared by the whole project.
Adjust before creating
Title, Jira project, issue type, priority, assignee and due date can be changed in the dialog before creating.
No duplicate tickets
Each issue links to at most one Jira ticket, and exporting again opens that ticket instead.

[02] Setup

How it works

Setup is one Atlassian sign-in from the project's Integrations settings. Atlassian has no app identity for such connections, so TesterArmy creates tickets through the account that connected Jira.

Open the Jira integration

In Project Settings, open Integrations, choose Jira and click Connect Jira.

Approve TesterArmy in Atlassian

Approve TesterArmy for an Atlassian account, where the OAuth request asks for issue read and write access plus user profile read for the assignee picker.

Pick project and issue type

Back in TesterArmy, pick the default Jira project and issue type for new tickets and save them once for the whole project.

Read the setup docsThe docs cover connecting an Atlassian account, the default project and issue type, creating tickets and priority mapping.

See it on your own app

START TESTING FOR FREE

[03] Related

Works with

Linear exports tickets too, and with both connected Create ticket becomes a menu. GitHub posts pull request checks, Slack receives group run summaries and coding agents debug failures over MCP.

LinearIssues the agents find become Linear tickets through one shared project-wide connection.GitHubThe GitHub App posts checks and comments on every pull request preview.SlackGroup run summaries with a link per run land in a Slack channel.MCP serverClaude, Cursor, Codex and VS Code create tests, start runs and debug failures.

[04] FAQ

Questions

TesterArmy fills the ticket with the issue's description, expected versus actual behavior, reproduction steps, a priority mapped from severity, a screenshot link and a link back to TesterArmy, and names the teammate who exported it.

One teammate approves TesterArmy for an Atlassian account and every project member can export tickets, no individual sign-in required. Tickets are created through that account and name the teammate who exported them.

Severity maps to Jira priority by name: severity 5 becomes Highest, 4 High, 3 Medium, 2 Low and 1 Lowest. Sites with custom priority schemes default to the scheme's middle priority, adjustable in the dialog.

If a Jira project's create screen requires custom fields that TesterArmy does not collect, export to that project fails. Pick a different Jira project or make those fields optional.

[05] Start with Jira

Send the next issue to Jira

Connect an Atlassian account once, save the default project and issue type, and every teammate can export issues as tickets from the Issues tab.