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

# Linear

> How to connect Linear to Pike and sync Linear issues into Pike tasks, with estimates turned into allocated hours and cycles into phases.

The Linear integration syncs Linear issues into Pike tasks in real time. Estimate points become allocated hours, and cycles can become phases, so delivery leads plan capacity and track margin on the work engineers run in Linear.

## Connect Linear

1. Go to **Workspace settings** → **Integrations** → **Linear**.
2. Click **Add integration**.
3. Authorize Pike in the Linear popup.
4. On the integration page, map each Linear team or project to a Pike project.

Only workspace admins can connect or disconnect Linear.

## Import data

On the integration page, click **Import data**. The stepper runs entities in dependency order, so cycles import as phases before the issues that sit in them. It skips entities whose **Read** toggle is off, names them, and links to sync settings.

## What syncs

Linear issues become Pike tasks.

| Linear | Pike | Notes |
| - | - | - |
| Title | Task title | |
| Description | Task description | |
| Assignee | Assignee | Matched by email |
| Due date | Due date | |
| Estimate points | Hours allocated | At the points-to-hours ratio you set. Default: 1 point = 4 hours |
| Labels | Labels | |
| Workflow state | Task status | Through an editable status mapping |
| Cycle | Phase | When **Map cycles to phases** is on |

### Source of truth

Once a record is linked, Linear owns the linked fields and Pike reads them back. Pike-only fields, such as project links, internal notes, allocations, and cost profiles, stay in Pike and are never overwritten.

### Schedule

Changes in Linear reach Pike in real time through Linear webhooks. **Import data** and **Refresh** always run on demand.

## Sync settings

While Linear is connected, the **What syncs with Linear** card sits under the top button row on the integration page. Each entity has a **Read** toggle (Linear to Pike). Toggles save immediately.

| Entity | Read | Send |
| - | - | - |
| Issues | Yes | Not available |

New connections start with **Read** on for everything.

## Synced records

Every synced record shows the Linear marker, "Last synced {time}" or "Not synced yet", and a **Refresh** action. **Refresh** shows only while **Read** is on for that entity.

Each synced task also shows the Linear identifier and an **Open in Linear** link.

### Sync issues

Records that fail to sync appear in the **Sync issues** list on the integration page, with the record, the reason, and a **Retry** action. The integration never deletes Pike data on its own. A record removed in Linear is marked "Removed in Linear" in Pike, never deleted.

## Disconnect

Disconnecting Linear stops syncing and keeps all imported data. Linked records keep their history.

## Permissions

Synced data respects Pike roles and private projects. A private project's tasks never sync out to anyone who cannot see the project in Pike.

## Limits

* Pike does not write back to Linear.
* Linear has no time log, so time logged in Pike stays in Pike.

## Related

* [Linear integration overview](https://usepike.com/integrations/linear): What syncs, how agencies use it, and FAQs.
* [Jira](https://usepike.com/docs/integrations/jira.md): Sync Jira issues and send worklogs.
* [GitHub](https://usepike.com/docs/integrations/github.md): Link pull requests to Pike tasks.
* [Allocations](https://usepike.com/docs/allocation/how-to-allocate.md): How allocated hours work.


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