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

# Linear

> Connect Linear to push Plans into engineering, keep their status in sync, and surface the customer demand behind the work.

Linear is where engineering builds. Lane's Linear integration connects planning to delivery: push a [Plan](/docs) into Linear as an issue, keep its status in sync as engineering works, and — on Business — send the customer demand behind a Plan so the team sees who's asking and why.

## Connect

Go to **Settings → Integrations → Linear** and connect your Linear workspace via OAuth. Available on **Pro and Business**.

## Push a Plan to Linear

From a Plan, use **Send to → Linear**. Lane creates a Linear issue from the Plan and links the two, so you can jump between them. The linked issue shows in the Plan's detail drawer.

## Keep status in sync

Map your Linear workflow states to your Lane [Plan statuses](/docs) in the Linear settings. When engineering moves an issue — say to "In Progress" or "Done" — the linked Plan's status updates in Lane automatically, so Lane always reflects where delivery actually is. Status sync is available on **Pro and Business**.

## Close the loop automatically

This is where it pays off. Once status sync is set up, shipping is the only action anyone has to take:

1. Engineering moves the issue to a shipped state in Linear.
2. The linked [Plan](/docs) flips to that status in Lane automatically.
3. Because the Plan reached a shipped status, [closing the loop](/close-the-feedback-loop) fires on its own — every [customer](/customers) behind the Plan's committed [feedback](/insights) is told, in the source they originally used: a reply in their [Slack](/slack) thread, a note on their [Intercom](/intercom) or [Zendesk](/zendesk) conversation.

Ship once in Linear, and the people who asked for it hear back — nobody has to remember to follow up, and nothing falls through.

## Customer requests

Linear has its own customer-requests feature, and Lane can feed it: the [feedback](/insights) a Plan commits — with the [customers](/customers) and revenue behind it — is pushed as Linear customer requests, so engineers see the real demand, not just a ticket. Customer requests are available on **Business** (and during the trial).

## FAQs

**Q: What gets created in Linear when I push a Plan?**\
A: A Linear issue, linked back to the Plan so status can sync between them.

**Q: Does the Plan's status update when engineering moves the issue?**\
A: Yes — once you've mapped Linear states to your Plan statuses, changes in Linear flow back onto the Plan.

**Q: What are customer requests?**\
A: The customer feedback committed to a Plan, pushed into Linear's customer-requests view so the demand and revenue behind the work are visible there. Available on Business.

**Q: Which plans include Linear?**\
A: Connecting and status sync are on Pro and Business; customer requests are on Business (and the trial).