Where results land

Linear integration

TesterArmy exports the issues its agents find as Linear tickets with one click, priority prefilled from severity.

START TESTING FOR FREE READ THE SETUP DOCS

[01] Ticket

What the ticket carries

The Linear ticket has the issue's description, expected versus actual behavior, reproduction steps, a priority mapped from severity, and a link back to the TesterArmy issue.

Linear · ENG-42

Discount code is not applied at checkoutSeverity 5ENG-42

Priority: Urgent
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
An admin authorizes the TesterArmy app once and every project member exports tickets with no individual sign-in.
No duplicate tickets
Each issue links to at most one ticket, and exporting again opens that ticket instead.
Ticket author
The TesterArmy app creates every ticket, and each one names the teammate who exported it.

[02] Setup

How it works

Setup is one screen in Project Settings under Integrations, where one approval and one default team serve the project. Revoking the app in Linear breaks exports until the project reconnects.

Connect Linear from Settings

In Project Settings, open Integrations, then Linear, and click Connect Linear.

Approve the TesterArmy app

Approve the TesterArmy app for the Linear workspace once, which anyone on the project can do, and the connection is shared.

Pick the default team

Back in TesterArmy, pick the default Linear team new tickets land in and save it once for the whole project.

Read the setup docsConnect Linear, pick the default team, create tickets with priority mapped from severity, and disconnect or revoke.

See it on your own app

START TESTING FOR FREE

[03] Related

Works with

Jira is the other ticket export. GitHub starts the pull request runs that find issues, Slack carries group run summaries, and coding agents debug failures over MCP.

JiraIssues the agents find become Jira 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

Each 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, naming the teammate who exported it.

One teammate approves the TesterArmy app for the Linear workspace once. After that every project member can export tickets without signing in, and TesterArmy never stores Linear credentials.

Priority comes from the issue's severity: 5 becomes Urgent, 4 High, 3 Medium and anything lower Low. Status defaults to the team's backlog, and you can change every field before creating the ticket.

Each issue links to at most one ticket. Exporting again opens the existing ticket instead of creating a second one, and the ticket key in the issue header links to Linear.

[05] Start with Linear

Turn the next issue into a ticket

Connect Linear once from Project Settings, pick a default team, and every issue the agents find is one click from a Linear ticket.