Skip to main content
TestSprite files tickets for failed tests into Jira or Linear, on demand for a single failure or automatically for every failure in a run. The same failure is never ticketed twice, and when the test recovers the ticket gets a follow-up comment.
A failed test case with the Create Bug Ticket button in the top-right

​
Before You Start

Ticketing files into Jira and Linear. You can connect one, both, or neither — each is configured independently per project. There is no GitHub Issues or built-in tracker for this feature.
Two things need to be in place:
  1. Connect the tracker at the workspace level. Go to Workspace Settings → Connections → Integrations and connect Jira and/or Linear via OAuth. This is a one-time, workspace-wide authorization. The per-project ticketing configuration (which team or project to file into) is separate and covered below.
  2. Pick where tickets land, per project. Jira files into a project (as a Bug); Linear files into a team.
Not every plan includes Jira and Linear ticketing. Compare plans on the pricing page.

​
Create a Ticket for a Single Failure

Open any failed (or blocked) test and file a ticket for just that failure. No project-wide setting needed.
1

Click Create Bug Ticket

On a failed test’s detail page, click Create Bug Ticket in the top-right. The button is available anywhere a failed run appears: the test case detail page, the execution detail page, and the test-cases list.
Create Bug Ticket button on a failed test case
2

Choose the tracker and destination

In the Create bug ticket dialog, pick Linear or Jira, then select the team (Linear) or project (Jira) the issue should be created in.
Create bug ticket dialog — Linear/Jira tracker toggle and a team picker
3

Confirm

The confirm step shows exactly what will be filed: the test name, and that the ticket includes the failure details and a link back to this run. The destination you pick is saved for this project, so the next ticket skips the picker.
Confirm step — Created in TestSprite (TES), with a Save-as-default checkbox
Saving the destination as the default does not turn on automatic filing — that stays off until you enable it in project settings (see below).
4

Open the ticket

Click Create Ticket. TestSprite files the issue and the button changes to Open TES-1234 (or the Jira key) — a direct link to the ticket.
After filing — the button becomes Open TES-3822 and a confirmation toast appears
Only failed or blocked tests can be ticketed. To file for every failure in a run at once, turn on automatic filing.

​
What’s in the Ticket

Secrets in the error and cause text are redacted before anything leaves TestSprite. Tickets currently link back to the run rather than attaching screenshots.

​
Auto-File Tickets for Every Failure

Once most of a project’s failures are real bugs, let TestSprite file them without a click.
1

Open Notifications & Ticketing

In the project, go to Project Settings → Notifications & Ticketing. Each connected tracker — Slack, Linear, Jira — has its own card.
Notifications & Ticketing settings — Linear and Jira cards with a File tickets for failed tests toggle
2

Pick the destination

On the Linear or Jira card, choose the Team (Linear) or Project (Jira) issues should be created in.
3

Turn on File tickets for failed tests

Flip File tickets for failed tests on and click Save Changes. From now on, when a run finishes, TestSprite opens one ticket per distinct failure.
Two settings shape how much gets filed:
Before you enable auto-filing the first time, triage the project’s failures manually once. A project with a backlog of genuine failures will open a ticket for each distinct one on the next run, potentially dozens at once. Clear or cluster the known failures first so it only files what’s genuinely new.

​
How Dedup Works

TestSprite never files the same failure twice, using two layers:
  • One ticket per failing test. A repeat failure of the same test updates its existing ticket with a “failed again” comment instead of opening a new one.
  • Same failure, one ticket across tests. Failures that share a root cause (the same error signature) are grouped onto a single ticket, within a 7-day window and up to 25 tests per ticket.
Manual and automatic filing dedupe against each other: if you manually file into the same destination the project is configured to auto-file into, a later automatic run recognizes the existing ticket and comments on it rather than duplicating.

​
When a Test Passes Again

When a previously failing test passes on a later run, TestSprite posts a recovery comment on its ticket and stops updating it. If a ticket covered several tests, the comment notes how many are still failing, and TestSprite keeps updating it until every test on it has recovered.
TestSprite posts the recovery comment and stops tracking the ticket. It does not transition or close the issue in Jira or Linear — your team’s own workflow owns the final status change. A later failure opens a fresh ticket, linked back to the recovered one.

​
Tips

While a suite is still flaky, use Create Bug Ticket on individual failures. Once the noise settles, turn on auto-filing.
Point ticketing at a dedicated Linear team or Jira project (a “QA triage” bucket) rather than your main backlog, and move the real ones over after review.
Keep the cap at a sane number (default 20) so a bad deploy that breaks half the suite can’t open a hundred tickets in one run.
You can enable Linear and Jira at the same time. Each files into its own destination with its own dedup, which helps when engineering lives in one tracker and QA in the other.

​
Where to Go Next

Slack Notifications

Post run results to a channel alongside ticketing

Test Schedules

Scheduled runs are the main source of auto-filed tickets

Test Detail

Where the Create Bug Ticket button lives

GitHub Integration

Run tests automatically on pull requests