Skip to main content
Turn issues from your project’s Issues tab into Linear tickets with one click. Each ticket carries the issue’s description, expected vs actual behavior, reproduction steps, severity-mapped priority, a screenshot link, and a link back to the TesterArmy issue.

How the connection works

Linear connects once per project: any project member authorizes the TesterArmy app in your Linear workspace (Linear may ask a workspace admin to approve it), and every project member can export tickets from then on, no individual sign-in required. TesterArmy never stores Linear credentials - the OAuth connection is managed by our auth provider and only requests read access and issue creation. Tickets are created by the TesterArmy app, not a personal account, and each ticket names the teammate who exported it. The project also stores one setting: the default Linear team new tickets are created in.

Setup

  1. Go to Integrations → Linear and click Connect Linear.
  2. Approve the TesterArmy app for your Linear workspace. Anyone on the project can do this; the connection is shared.
  3. Back in TesterArmy, pick the default Linear team tickets should land in and save it. This is shared by the whole project, so it only needs to be set once.

Creating tickets

  1. Open an issue from the project’s Issues tab.
  2. Click Create ticket in the issue header. If more than one tracker is connected, or none is, the button becomes a menu - pick Linear. A dialog opens where you set the ticket title plus the Linear team, status, assignee, priority, and due date. The title is prefilled from the issue name, the team from the project default, status defaults to the team’s backlog, and priority is prefilled from the issue’s severity - all of them can be changed before creating.
  3. Click Create ticket in the dialog. The ticket key (for example ENG-42) appears in the issue header and links to Linear.
Each issue links to at most one ticket - exporting again is prevented, and the existing ticket is surfaced instead. The prefilled priority maps from severity: severity 5 becomes Urgent, 4 becomes High, 3 becomes Medium, and lower severities become Low.

Auto-export

Turn on Auto-export issues in the Linear card to skip the dialog: after each failed run, each open issue the run found that has no ticket yet is exported to the default team. False positives and step failures are never exported, and a regression that reopens keeps its existing ticket. Auto-exported tickets get the severity-mapped priority and name no exporter. The switch can’t be turned on until a default team is saved. Reconnecting clears the default, which pauses auto-export (the switch stays on) until you pick one again. Only one tracker auto-exports at a time, because an issue links to one ticket: turning it on for Linear turns it off for any other tracker. Disconnecting Linear turns it off. Once it’s on, Environments picks which runs export: Production, PR Preview, each saved environment, and Unsaved URLs (staging or custom runs on a URL that is not a saved environment; a URL run started with no environment counts as PR Preview). Production and PR Preview are on by default; projects that turned on auto-export before the picker existed keep their earlier coverage, every environment except PR Preview. A newly saved environment starts off, so it only files tickets once you pick it.

Disconnecting

Disconnect Linear in the project’s integration settings unlinks the project and removes the stored connection once no other project uses it. Already-created tickets are unaffected. You can also revoke the TesterArmy app from Linear’s workspace settings at any time; exports will fail until the project reconnects.