Skip to main content
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 or a Doc to Linear as an issue, or link a Signal to the issue that already exists, 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. Often engineering already has an issue for the problem before the Signal reaches them. Instead of creating a second one, link the Signal to it, so the customer evidence lands on the issue the team is already working from. On a Signal, open the Send to menu and choose Link existing → Linear issue, then search for the issue or paste its key or link. Lane links it the same way a sent issue is linked:
  • An Open Signal becomes Accepted, and the issue’s live status shows on the Signal.
  • The issue gets a link back to the Signal, and the feedback behind the Signal is added as customer requests, skipping any the issue already has.
  • The issue’s own title and description are left as they are.
Several Signals can link to the same issue, for example when one fix answers more than one problem. On an accepted Opportunity, Send to Linear → Existing issue links its Signals in one go: pick an issue for each, or use one issue for all of them. The linked issue shows as a tag above the Signal’s title. Hover it to open the issue or Unlink it; unlinking only removes the link in Lane, and the issue stays as it is in Linear.

​
Pull requests on the issue

If your team has connected Linear to GitHub in Linear, Linear attaches the pull requests for each issue. Lane shows them under the issue, on the Signal and on the Opportunity, with their state (open, draft, merged or closed), so you can see the code moving without leaving Lane. They are there to see; the issue’s status is still what moves the Signal. To link pull requests to a Signal directly, without a Linear issue, see GitHub.

​
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 fires: every customer behind that feedback is told in the place they asked, with a reply in their Slack thread or a note on their Intercom or 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 Agents

  • 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.
  • Ask Lane can also link a Signal to an existing issue or create its issue, just like Send to and Link existing: “link ENG-123 to this Signal”. If the conversation has read customer feedback, it asks for your approval first.
  • Agents 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 agent makes Linear changes without asking, for example commenting a pre-build check on an issue as it moves into progress, or linking Signals to their issues and creating issues for them when its instructions say so.

​
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: Can I link a Signal to an issue that already exists instead of creating one?
A: Yes. Choose Link existing → Linear issue from the Signal’s Send to menu. A linked issue works just like a sent one: status sync, customer requests and closing the loop all apply. 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.