Fully Agentic Test Case Management Tool
Write, Track and Manage Every Manual or Automated Tests in One Agentic Test Management Platform with TestMu AI Test Manager.
Link Linear Issues With Test Manager
Test Manager now syncs with Linear both ways: link issues to test cases, runs and steps, and test cards carry the latest results onto the Linear issue.
Last Updated on:
Test Manager now syncs with Linear in both directions. You link a Linear issue to a test case, a test run, a test run instance, or an individual step, and Test Manager puts test cards back on that Linear issue carrying the latest results.
Each direction stays current on its own. Issue details are fetched from Linear every time you open the test artifact rather than stored, so the status beside a failing test is the status in Linear at that moment, and the cards on the Linear side update within seconds of a result being recorded. Linking needs the Linear integration connected first, and the cards stay off until the owner of that connection turns them on.
What Can You Link a Linear Issue To?
Linking works at four levels, which matters because a failure is rarely about a whole test case. The step that broke is usually the thing the bug describes.
- Test case - the issue follows the case itself, wherever it is run.
- Test run - the issue belongs to one execution of a set of cases.
- Test run instance - the issue attaches to one case inside one run, which is where most triage lands.
- Individual step - the issue points at the exact step that failed.
One Linear issue can be linked to any number of test cases, runs, and instances, and one test artifact can carry any number of Linear issues. Linking the same issue to the same artifact twice does not create a duplicate, so repeated linking during a triage session is safe.
How Do You Link a Linear Issue?
Connect Linear to your account first. Until it is connected, Linear cannot be selected as a source, and the Link Issue dialog shows the connection state of each tracker so you can see why. The setup steps are in the documentation on Linear app integration.
- Open the Issues tab inside a test case or a test run and click Link Issue.
- Select Linear as the source.
- Enter the Linear issue ID or paste its URL, then click Link Issue.

One boundary governs what you can find: searching and linking are limited to the Linear projects selected during setup. Issues from any other project are not returned, so an issue that will not appear is usually a scope question rather than a search problem.
Note: Test Manager connects requirements, test cases, runs, and defects in one traceability view across 120+ integrations. Start free with TestMu AI
What Does a Linked Issue Show?
A linked issue lists its title, identifier, issue type, status, priority, creation date, and creator, and clicking it opens the issue directly in Linear.

The detail that changes how much you can trust the view: Test Manager does not store any of these fields. They are fetched from Linear every time you open the test case, test run, or instance, so the status beside a failing test is the status in Linear at that moment, not a copy taken when someone linked it. Stale defect status is the usual reason a traceability report has to be re-checked by hand, and this removes that step.
Linked issues are grouped by tracker, so Linear issues sit under Linear alongside any Jira or Azure DevOps issues on the same test artifact. A search box and Status and Issue Type filters narrow a long list, which matters on a run that accumulated issues across several triage passes. For the wider practice this supports, test management explains where defects sit in the cycle, and the guide to defect management covers how defect records and test evidence fit together.
What Do Test Cards Show in Linear?
Test cards are blocks Test Manager adds under Resources on a linked Linear issue. They carry the latest result, the steps behind it, and the coverage of every test linked to that issue, and they refresh on their own.

Three kinds of card exist, and which ones appear depends on what you linked.
| Card | Added when you link | What it carries |
|---|---|---|
| Test case card | A test case | The latest result with the run, browser and OS it came from, earlier results from other runs, and the preconditions and steps |
| Test run card | A test run | The worst result in the run so far, progress and pass rate, counts of passed, failed and not started, and every result grouped by browser and OS |
| Coverage card | Anything, one per issue | Health across all linked tests, the tests that need attention with where they failed, a chart of latest results, and all tests, executions and runs |

Every result on a card carries a colored marker, so a failure reads at a glance without opening anything. Clicking a card expands it, and Open in on the card goes to the same test case or test run in Test Manager.
Cards update within seconds when a result is recorded in a test run, a test case or run is renamed, or a case's steps, preconditions or priority are edited. Linking or unlinking a test changes them the same way. If a card looks stale, Sync test cards in the Linear App connection details refreshes every linked issue at once.
One limit is worth stating plainly: cards carry information from Test Manager to Linear and not the other way. A card cannot be edited in Linear, so the change is made in Test Manager and the card follows. That is also what makes the coverage card trustworthy on a release issue, because nothing on it was typed by hand.
How Do You Turn On Test Cards in Linear?
Test cards are off by default. The owner of the Linear connection opens Info on the Linear App card in Integrations, switches on the Test cards in Linear toggle, and waits for that section to report Healthy.
- In Integrations, click the three-dot menu on the Linear App card and choose Info.
- Switch on the toggle in the Test cards in Linear section.
- Wait a few seconds until the section shows Healthy.

Turning the toggle on is retroactive. Every Linear issue that already has tests linked in Test Manager gets its cards, so an existing project does not need relinking.
One step belongs ahead of all three: share the connection with your organization, from the same three-dot menu on the Linear App card. On a shared connection an admin turns cards on once and the setting covers every test the team links, against one API key and one place to check sync health. A teammate who connected Linear with their own key is on a separate connection and has to turn cards on for it themselves, or drop it and use the shared one.
Switching cards off stops updates and leaves the cards already in Linear exactly as they are. Turning them back on brings every linked issue up to date again. The full reference, including each result color and what to do when the connection reports Needs attention, is in the documentation on test cards in Linear.
What Happens When Linear Changes?
Because the details are fetched rather than stored, the useful question is what you see when Linear cannot answer. Each situation has a defined behaviour.
| Situation | What happens |
|---|---|
| Linear is not connected to your account | Linear cannot be selected in the Link Issue dialog until you connect it |
| The issue belongs to a project you did not select during setup | It is not returned in results and cannot be linked |
| Linear is temporarily unreachable | The issue is shown with the details last retrieved, along with a notice that they could not be refreshed. The next view retries |
| The issue is archived in Linear | The issue is identified as archived and can still be linked |
| The issue has been deleted in Linear | The issue is reported as unavailable and can be unlinked |
| Linear is disconnected from your account | Linked Linear issues are no longer shown. They become visible again if you reconnect the same Linear workspace and projects |
The disconnect row is the one worth noting before an integration change. Links are not destroyed when the connection drops, they stop being displayed, and reconnecting the same workspace and the same projects brings them back.
How Does Unlinking Work?

The unlink button sits on the right side of each linked issue. Unlinking removes the association in Test Manager only, and the issue itself stays in Linear, so clearing a wrong link during triage carries no risk to the tracker. The test's card leaves the Linear issue with it, and once nothing is linked to that issue anymore all of its cards go too.
That separation is what makes linking cheap to use. An issue linked to the wrong instance can be removed and relinked to the right one without touching the Linear record, and a tester who links generously during a run is not creating cleanup work for whoever writes the release report. The structure of the artifacts being linked is covered in the test case guide.
For the step-by-step setup, including what happens when Linear is unreachable or an issue is archived, read the documentation on link Linear issues with Test Manager.
Conclusion
Connect Linear, share the connection, turn on test cards, then link at the instance or step level on your next failing run rather than at the case level, because that is where the issue and the evidence actually correspond. Link the run itself to the release issue, and that issue shows the pass rate for the whole release.
Linear joins Jira and Azure DevOps as a tracker you can trace from inside test manager, and the test management software keeps requirements, cases, runs, and defects in one workspace. If you also log new bugs to Linear from a run, the earlier walkthrough on bug tracking with the Linear app covers that side of the integration.
Author
Bhavya Hada is a Community Contributor at TestMu AI with over three years of experience in software testing and quality assurance. She has authored 20+ articles on software testing, test automation, QA, and other tech topics. She holds certifications in Automation Testing, KaneAI, Selenium, Appium, Playwright, and Cypress. At TestMu AI, Bhavya leads marketing initiatives around AI-driven test automation and develops technical content across blogs, social media, newsletters, and community forums. On LinkedIn, she is followed by 4,000+ QA engineers, testers, and tech professionals.
Reviewer
Abhishek Mishra is a Technical Product Manager at TestMu AI, where he owns Test Manager, the test management product. He has over 8 years of experience in product management and market analysis. His expertise spans across AI-native software testing, product strategy, and analytics. Previously, Abhishek served as the Product Lead at IndiaClan and co-founded Gartley618 Technologies, where he led innovative projects in quantitative trading and blockchain. He holds a B.Tech degree.
Linear Issue Linking FAQs
Did you find this page helpful?
More Related Blogs
TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance
- Advanced access controls
- Advanced data retention rules
- Advanced Local Testing
- Premium Support options
- Early access to beta features
- Private Slack Channel
- Unlimited Manual Accessibility DevTools Tests

















