# Issue trackers: Trello, Jira, GitHub Issues, and Linear

Turn a failing run into a ticket on the board your team already works from.

> **Plan:** available on the Pro plan and above.

A notification tells you something broke. A ticket makes sure somebody picks it up. Connecting an issue tracker means a failing run can open an issue automatically, on the board your team already looks at, without anybody having to transcribe the failure by hand.

![A failed run with the three-dot menu open, showing Send to Trello, Send to Jira, and Send to GitHub.](https://testsnag.com/images/docs/notifications/issue-trackers-1-send-to.r1.jpg)

Marked on the screenshot:
- Open the three-dot menu on the run.
- Send this failure to Trello as a card.
- Or to Jira as an issue.
- Or to GitHub Issues.
- The failure that becomes the ticket, with its error already captured.

## Connecting a tracker

Connect Trello, Jira, GitHub Issues, or Linear once from the Integrations page, under its Project Management tab. The page groups what it offers into Communication, Development, and Project Management, so you are picking from a handful of relevant cards rather than scanning everything at once. Each connection is workspace-level and authorises Testsnag to create and update issues on your behalf. After that, individual tests choose whether to use it.

## Choosing a target

A connection alone does not create anything. On the Integrations page, use the Manage button on the card to pick where issues should land: a Trello board and list, a Jira project and issue type, a GitHub repository with optional labels, assignees, and a milestone, or a Linear team with an optional project, labels, priority, and assignee. Then, in a test’s settings, set whether issues are created on failure, whether the issue gets a comment when the test passes again, or both.

You can also raise one by hand from a run you are looking at. Open the three-dot menu on the run and pick Send to Trello, Jira, GitHub, or Linear. A dialog opens with the title and description already filled in from the failure, and the destination set to your saved target. Edit any of it before you send. If an issue for that test is already open, the dialog says so, and what you write is added to that issue as a comment instead of opening a second one.

## Linear

Linear issues and comments are created under the Linear account of the person who connected it, and the Linear card on the Integrations page shows who that is. If that person leaves your Linear workspace or revokes access, the integration shows as disconnected and anyone who manages integrations can reconnect it with their own account. Several Testsnag workspaces can connect the same Linear workspace. Every failing run is attached to its Linear issue as a link back to the run.

## Status is kept in step

Testsnag keeps track of the issues it has opened. When the test passes again, the linked issue is updated rather than left to rot, and repeated failures of the same test do not spawn a new ticket every time. Closing or completing the issue in the tracker resolves it on the Testsnag side too, so the next failure opens a fresh one. That is what stops an integration like this from becoming its own source of noise.

Issues are tracked per test per [environment](https://testsnag.com/docs/building-blocks/environments.md). A failure on Staging and a failure on Production open separate issues, and a pass on Staging only updates the Staging issue.

> **Note:** This article covers Testsnag’s side of each integration. For how boards, projects, teams, and issue types work in Trello, Jira, GitHub, or Linear themselves, see their own documentation.