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

# Linear

> File Problems as Linear issues, keep their status in sync both ways, and ask @Moda about a Problem from inside Linear.

The Linear integration turns a [Problem](/dashboard/problems) into a Linear issue that carries its cause, impact, and evidence, and keeps the two in step: completing the issue marks the Problem fixed, and if Moda sees the Problem come back, the issue reopens with the new evidence. It is in preview; ask Moda support to enable it for your workspace.

## Connect Linear

1. Open **Integrations** and select **Connect Linear**. Only workspace admins can connect.
2. Approve the Moda app in Linear. Moda is installed as an app, so issues and comments are authored by Moda and show "Your name (via Moda)" when you file them, and the integration keeps working if the person who connected it leaves.
3. Back on **Integrations**, choose the team Problems are filed in. Optionally pick a project and labels, and decide how Linear status flows back:

| Setting | Default | What it does |
| - | - | - |
| **Issue completed in Linear** | Mark the Problem fixed | Moda records *mark fixed*; the Problem moves to **Fixed** at the next analysis run and Moda monitors it for recurrence. |
| **Issue canceled in Linear** | Do nothing | Optionally dismiss the Problem. Dismissing can't be undone in Moda, so it is off by default. |
| **Problem comes back** | Move to the team's first *Todo* state | When a fixed Problem recurs, Moda moves its closed issue back to this state and comments the new evidence. |

**Disconnect** revokes Moda's access in Linear and deletes the stored credentials. Existing issues stay in Linear; their status stops syncing until you reconnect.

## File a Problem

On a Problem, select **Create Linear issue**. Edit the title, team, and priority, then **Create issue**. The issue contains:

* the cause statement and current impact (users, traces, rank, status),
* the top five pieces of evidence, each linked to its trace,
* a link back to the Problem, attached to the issue.

Each Problem has at most one issue. Filing again, from another tab, the CLI, or an automation, returns the issue that already exists. To track a Problem with an issue your team already has, switch to **Existing issue** and paste its ID (`ENG-123`) or URL. The chip in the Problem header shows the issue's live Linear state; **Unlink issue** removes Moda's attachment and leaves the issue in Linear.

## How status syncs

| When | Then |
| - | - |
| The issue moves to a *completed* state | The Problem is marked fixed (unless you turned this off). |
| The issue is canceled | Nothing, or the Problem is dismissed if you opted in. |
| The issue is deleted, or Moda's attachment is removed | The link is removed in Moda. |
| Moda marks the Problem fixed | Moda comments that it is monitoring for recurrence. |
| The Problem comes back | The issue moves back to an open state and Moda comments the new impact and evidence. |
| The Problem is resolved | Moda comments on the issue. |
| The Problem is merged into another | The issue follows the surviving Problem, or points to the surviving Problem's own issue. |
| A [fix](/dashboard/fixes) PR for the Problem is opened | Its description says `Refs ENG-123`, so Linear links the PR without closing the issue on merge. |

Moda-to-Linear updates run every 15 minutes. Linear-to-Moda changes are recorded immediately and applied at the next analysis run.

## Ask @Moda in Linear

Mention **@Moda** in a comment on an issue (or delegate the issue to Moda) to get the linked Problem's current status, impact, cause, and top evidence. Mention @Moda with a Problem's URL to link an issue your team filed by hand to that Problem.

## Automations

With both Slack automations and Linear enabled, an automation can file in Linear instead of posting to Slack. Choose **Linear** as the destination and pick a team and priority:

* Problem automations (**New problem**, **Problem gets worse**) use the Problem's one issue: the first alert files it, later alerts comment on it.
* Other alerts file one issue each, and a recovery comments on the issue its alert filed.

## CLI and MCP

* `moda problem-linear <problem_id>` (MCP `problem_linear`) shows the linked issue.
* `moda problem-linear-file <problem_id>` (MCP `problem_linear_file`) files the issue, or links one with `--issue=ENG-123`.

Both use your API key and need the integration connected. See the [parity map](/mcp/parity).


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