> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testdino.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Linear Integration
> Create Linear issues from failed or flaky Playwright tests in TestDino.
export const VideoSchema = ({name, description, thumbnailUrl, uploadDate, duration, contentUrl, embedUrl}) => {
const schema = {
"@context": "https://schema.org",
"@type": "VideoObject",
name,
description,
thumbnailUrl,
uploadDate,
...duration ? {
duration
} : {},
...contentUrl ? {
contentUrl
} : {},
...embedUrl ? {
embedUrl
} : {},
publisher: {
"@type": "Organization",
name: "TestDino",
logo: {
"@type": "ImageObject",
url: "https://docs.testdino.com/logo/light.svg"
}
}
};
return ;
};
The Linear integration creates prefilled issues in Linear directly from failed or flaky tests in TestDino. Each issue includes the test name, error details, failure history, code context, console output, screenshots, and links to the TestDino run and Git commit.
This is a **user-level** integration. Each team member connects their own Linear account and creates issues under their own identity.
**Warning**
Available on TestDino **Team** and **Enterprise** plans.
## Prerequisites
* A TestDino project with test runs uploaded ([Getting Started](/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.
**Note**
The 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.
Navigate to a **Test Run** in TestDino.
Choose a failed or flaky **test case** from the run.
Click **Raise Issue** and select **Linear**.
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.
TestDino shows a confirmation with the Linear issue key and internal ID with a copyable URL. Click **View in Linear** to open the issue and continue triage.
## 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
* 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
* TestDino automatically refreshes OAuth tokens when supported by the provider. If you still see authorization errors, click **Disconnect** on the Linear card, then reconnect and re-authorize
* Ensure your Linear account has permission to create issues in the target team
* The button appears on failed or flaky test cases inside a test run detail view. Open a test run and click into a specific failed test
* Verify the Linear integration is connected for your account in **Settings → Integrations**
* 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
### 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.
