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

# Linear

> Connect Linear to LaunchSafe to automatically create and track issues from vulnerability findings, syncing security work into your team's workflow.

The Linear integration enables your team to create Linear issues directly from LaunchSafe findings, fitting security remediation into your existing engineering workflow.

## Prerequisites

* A Linear workspace with admin access
* An active LaunchSafe workspace

## Setup

<Steps>
  <Step title="Navigate to Integrations">
    In the LaunchSafe dashboard, go to **Integrations** in the sidebar and locate the **Linear** card.
  </Step>

  <Step title="Connect Linear">
    Click **Connect Linear**. You'll be redirected to Linear's OAuth authorization page.
  </Step>

  <Step title="Authorize LaunchSafe">
    Grant LaunchSafe access to your Linear workspace. LaunchSafe requests permission to:

    * Read teams and projects
    * Create, read, and update issues
    * Add comments and attachments
  </Step>

  <Step title="Select your team">
    Choose the Linear team where security issues should be created. You can also configure:

    * **Default project** — assign issues to a specific project (e.g., "Security Backlog")
    * **Labels** — automatically apply labels like `security` or `vulnerability`
    * **Cycle** — optionally assign issues to the current cycle
  </Step>
</Steps>

## Creating issues from findings

From any finding in LaunchSafe:

1. Click the **Create Linear Issue** button on the finding detail page
2. Review the pre-populated fields
3. Optionally adjust team, project, assignee, or cycle
4. Click **Create** — the issue is created in Linear
5. A link to the Linear issue appears on the finding

### Field mapping

| LaunchSafe field       | Linear field          | Content                                                   |
| ---------------------- | --------------------- | --------------------------------------------------------- |
| Title                  | Title                 | Vulnerability title (e.g., "SQL Injection in /api/login") |
| Severity               | Priority              | Mapped automatically (see below)                          |
| Description + Evidence | Description           | Full Markdown-formatted description with code blocks      |
| Category               | Labels                | Vulnerability category label                              |
| Remediation            | Description (section) | Fix instructions with code examples                       |
| LaunchSafe URL         | Description (link)    | Direct link to the finding                                |

### Priority mapping

| LaunchSafe severity | Linear priority                               |
| ------------------- | --------------------------------------------- |
| Critical            | **Urgent** — requires immediate attention     |
| High                | **High** — should be addressed this cycle     |
| Medium              | **Medium** — plan for upcoming cycle          |
| Low                 | **Low** — address when convenient             |
| Info                | **No priority** — informational, triage later |

### Why Linear works well for security issues

Linear's workflow model aligns naturally with vulnerability remediation:

* **Triage** → finding discovered, issue created, awaiting review
* **Backlog** → finding reviewed, prioritized for a future cycle
* **In Progress** → developer actively working on the fix
* **Done** → fix deployed, verified by rescan

LaunchSafe's severity-to-priority mapping ensures critical vulnerabilities surface at the top of your team's queue automatically.

## Bulk issue creation

Select multiple findings from the Findings page and create Linear issues in bulk. Each finding becomes a separate issue in your configured team, with appropriate priority and labels applied.

## Issue tracking

Once a Linear issue is created from a finding, LaunchSafe tracks the association:

* The finding shows a **Linear issue link** for quick navigation
* Duplicate issue creation is prevented (you'll see a warning if an issue already exists)
* When you rescan and the vulnerability is resolved, the finding is marked as fixed — you can close the Linear issue

## Disconnecting

Go to **Integrations** → **Linear** → **Disconnect**. Existing Linear issues are not affected.