What you’ll learn
- How to connect your Linear workspace to a TestDino project
- How to create prefilled issues from failed or flaky tests
- How to manage the integration (sync, disconnect, change defaults)
Prerequisites
- A TestDino project with test runs uploaded (Getting Started)
- A Linear account with permission to create issues
- A Linear team to file issues into
Connect Linear to TestDino
1. Open the Integrations page
Go to Settings → Integrations in your TestDino project. Find the Linear card and click Connect.2. Authorize your Linear account
TestDino redirects you to Linear to authorize access. Sign in and approve the request. TestDino requests permission to read workspaces, teams, and create issues.3. Configure defaults
After authorization, select the default Workspace and Team where issues will be created. You can change these per issue when creating a bug report.
NoteThe default team is a convenience setting. You can select a different team each time you create an issue.
Create a Linear Bug Report
Create Linear issues directly from failed or flaky test cases. Each issue includes test metadata, so your team has full context without opening separate reports.Configure & Create issue
Select the Workspace and Team. Set Issue Type, Priority, Labels, and Assignee as needed. Review the Summary and Description (auto-generated from failure data). Use the Write/Preview toggle to verify formatting. Click Create to file the issue in Linear.

What TestDino Pre-fills
Every issue is created with structured context so the developer receiving it has everything needed to investigate.| Section | Field | Pre-filled Content |
|---|---|---|
| Linear Fields | Workspace and Team | Default from Settings is preselected |
| Issue Type | Linear issue types | |
| Priority | Linear priority values | |
| Labels | Optional routing labels | |
| Assignee | Optional routing assignee | |
| Summary | Title based on test name with run context | |
| Description | Test Details | File, branch, commit author/message, environment, run ID, duration, attempts |
| Why It Failed | Failure cluster and the exact step or locator | |
| Last Attempt Snippet | Short code context around the failing line | |
| Recent History | Failure frequency in the selected period | |
| Console Tail | Recent relevant console output lines | |
| Links | TestDino run, Git commit, CI job | |
| Review | Write/Preview | Verify formatting before submitting |
| Screenshots | Listed thumbnails; attach more if needed |
Troubleshooting
Teams or labels not showing in the form
Teams or labels not showing in the form
- Click Sync on the Linear card in Settings → Integrations to refresh teams, labels, and templates from Linear
- Verify your Linear account has access to the workspace and team you expect to see
Authorization failed or expired
Authorization failed or expired
Create Bug Report button not visible
Create Bug Report button not visible
Issue created but formatting looks wrong
Issue created but formatting looks wrong
- Use the Write/Preview toggle in the bug report form to verify markdown formatting before submitting
- Linear renders markdown in issue descriptions. Complex code blocks may need manual adjustment

