> ## Documentation Index
> Fetch the complete documentation index at: https://www.minitap.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Linear

> File a Linear issue from any Minitap finding, with the steps to reproduce and the recording, or link the issue you already have and see its status.

Connect Linear and any finding becomes a Linear issue in two clicks: an [issue](https://www.minitap.ai/docs/minitest/triage/issues.md), a [UI/UX suggestion](https://www.minitap.ai/docs/minitest/triage/suggestions.md) or a failed criterion in a [run report](https://www.minitap.ai/docs/minitest/runs/run-report.md). If your team already tracks it, link the existing issue instead, and its Linear status shows next to the finding.

## Connect Linear

**1. Open Integrations**

Go to **Settings → Integrations** (also reachable from an app's **App settings → Integrations**). A workspace owner or admin can connect Linear.

**2. Authorize Minitap**

Click **Connect** on the **Linear** row and approve access with your Linear account. Minitap lists the teams that account can see.

You can also connect from a finding: before any tracker is connected, its **Ticket** menu offers **Connect Linear**, and the ticket form opens again when you come back.

## File an issue from a finding

**1. Open the Ticket menu**

Click **Ticket** on the issue, the UI/UX suggestion or the failed criterion. With several trackers connected, pick **Linear** at the top of the menu.

**2. Create a new issue**

Click **Create a new Linear ticket**, then pick the **Team**: type a few letters to search your teams. Minitap loads that team's fields.

**3. Check the fields and create**

Adjust what Minitap preset, then click **Create ticket in Linear**. The finding now shows the issue's key and status, and links to it.

Minitap presets the fields so the issue lands ready to pick up. You only see the fields your team has:

| Field | Preset |
| - | - |
| **Priority** | **High** for a Critical finding, **Medium** for a Warning one |
| **Labels** | Your team's **Bug** label, when it has one |
| **Project** | The team's first project |
| **Status** | The team's backlog state |
| **Assignee** | Nobody |

### What the issue contains

For an issue or a failed criterion, the Linear issue is titled with what went wrong and holds:

* A **View in Minitap** link and a **Watch the recording** link.
* **What happened**, in Mini's words.
* **Root cause analysis**, with the steps to reproduce, the expected and actual behavior when Mini wrote them down.
* A **Context** table: the scenario, the acceptance criterion, the platform, the build and the severity.

For a UI/UX suggestion, it holds what Mini found, the screen, the kind of suggestion, its severity, the scenarios it was seen in, the platform, Mini's notes, and a **View in Minitap** link.

## Link an issue you already have

Open the **Ticket** menu and search instead of creating: type an issue key (`ENG-142`), a few words, or paste the issue's link. With an empty search, the menu shows the recently updated issues. Pick one and the finding is linked to it.

A finding holds one ticket at a time. To change it, open the issue in the **Issues** tab and click **Unlink ticket**: the link goes, and the issue stays in Linear.

## Status in Minitap

Every linked finding shows the issue's key and its current Linear status, such as `ENG-142 · In Progress`, and opens the issue in Linear on click. Minitap reads the status from Linear each time it shows it. If the issue was deleted in Linear, Minitap drops the link.

The finding keeps its own triage status in Minitap: triage it in the [Issues](https://www.minitap.ai/docs/minitest/triage/issues.md) tab.

## From the CLI

The same actions work from the `minitest` CLI, for scripts and coding agents:

```bash theme={"theme":{"light":"github-light","dark":"vesper"}}
# Your Linear teams, with their IDs
minitest --app <app-id> issues ticket targets linear

# File an issue in a team, or link one you have
minitest --app <app-id> issues ticket create <issue-id> --provider linear --target <team-id>
minitest --app <app-id> issues ticket link <issue-id> --provider linear --ticket ENG-142
```

`issues ticket fields linear --target <team-id>` lists the fields you can set with `--field KEY=VALUE`. See the [CLI reference](https://www.minitap.ai/docs/minitest/reference/cli-commands.md).

## Next steps

> [card] [Triage issues](https://www.minitap.ai/docs/minitest/triage/issues.md)
>
> Decide which failures deserve a ticket.

> [card] [UI/UX suggestions](https://www.minitap.ai/docs/minitest/triage/suggestions.md)
>
> The polish ideas Mini flags while it tests.

> [card] [Jira](https://www.minitap.ai/docs/minitest/integrations/jira.md)
>
> The same tickets in Jira, plus @Mini in comments.

> [card] [Notion](https://www.minitap.ai/docs/minitest/integrations/notion.md)
>
> Specs for Mini to read, and findings filed as pages.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.