> ## 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

> Send Signals and Docs to Linear, show engineers the customers behind each issue, and let shipping in Linear tell the customers who asked.

Linear is where engineering builds, and it's where customer context usually gets lost: an issue says what to build, not who asked for it or what's at stake. Lane's Linear integration carries that context across. Send a [Signal](/signals) or a [Doc](/docs) to Linear as an issue, show engineers the customers and revenue behind it as Linear customer requests, and let issue status flow back so that shipping in Linear tells the customers who asked.

## Connect

Go to **Settings → Integrations → Linear** and choose **Connect**. Available on **Pro**.

Lane connects as its own Linear app, so the changes Lane makes show as Lane, and issues your team sends show as "*your name* (via Lane)". This needs a Linear workspace admin. If you aren't one, choose **Connect as yourself** instead, and Lane's changes will show under your name. If a team is private in Linear, give Lane access to it there.

## Send to Linear

From a Signal or a Doc, choose **Send to Linear**:

* **From a Signal**, the issue carries the Signal's name and summary, with a link back to the live Signal in Lane.
* **From a Doc**, the issue carries the Doc's title and content.

Sending an Open Signal marks it **Accepted**. From then on the button shows the issue's live status, so you can see where delivery is without leaving Lane.

## Customer requests

Linear has its own customer requests, and Lane fills them in. When you send, each piece of feedback behind the Signal or Doc becomes a customer request in Linear: the customer, with their revenue and size, and the request in their own words. Engineers see real demand next to the work, not just a ticket.

This is on by default; the setting is **Include insights as customer requests** in the Linear settings. Feedback that isn't linked to a customer with a domain isn't sent.

## Keep Signals in step with Linear

Under **Status sync** in the Linear settings, turn on **Sync Linear issue status to Lane Signal status**, then add rules that map Linear statuses to Lane's **Accepted** or **Closed**. When engineering moves an issue, the linked Signal moves with it, so Lane reflects where delivery really is. Status sync is off until you turn it on.

## Close the loop automatically

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

1. Engineering moves the issue to a status you mapped to **Closed**.
2. The linked Signal becomes Closed in Lane, and its feedback is marked done.
3. [Closing the loop](/close-the-feedback-loop) fires: every [customer](/customers) behind that feedback is told in the place they asked, with a reply in their [Slack](/slack) thread or 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.

## Linear in Ask Lane and Automations

* **Ask Lane** can read your issues, projects, cycles and comments to answer questions like "what's in progress for SSO?". When you ask, it can also create or update an issue or add a comment; each change is shown on a card for you to approve before it's sent. It never deletes or archives anything.
* **[Automations](/automation)** can start when an issue's status changes (**Issue status updated**, narrowed by team or status if you like), and can use Linear as a connector. With **Read and write**, an automation makes Linear changes without asking, for example commenting a pre-build check on an issue as it moves into progress.

## FAQs

**Q: What gets created in Linear when I send a Signal or Doc?**\
A: A Linear issue, linked back to Lane, with the feedback behind it added as customer requests.

**Q: Does the Signal update when engineering moves the issue?**\
A: Yes, once you've turned on status sync and mapped Linear statuses to Accepted or Closed.

**Q: Why do Lane's changes show under my name?**\
A: Linear was connected with **Connect as yourself**. Ask a Linear workspace admin to connect Lane as its own app so its changes show as Lane.

**Q: Which plans include Linear?**\
A: Pro (and the trial), including customer requests.


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