Productlane is built on Linear. Issues, projects, customers, and your roadmap sync both ways, so your inbox, public roadmap, and changelog show the current state in Linear.
Sign in to Productlane with your Linear account, or connect Linear from Settings → Integrations → Linear.
Connect with an account that has admin rights in Linear for full access to teams, customers, and projects.
The connection refreshes itself, so you stay connected without re-authenticating. Disconnecting requires an admin role in Productlane.
Select which Linear teams are visible in Productlane. Only their issues and projects sync.
Private Linear teams are not available. Make the team public in Linear to use it.
Set a default team to speed up creating issues and projects. It is preselected in the create dialogs and used whenever an issue is created automatically.
Two-way, in real time:
Issues - title, description, status, priority, assignee, and due date stay in sync. Create an issue in either tool and link it to a thread.
Projects - name, description, status, team, icon, and color stay in sync.
Customers - name, revenue, tier, size, status, and domains sync both ways. With Auto-create customers on, every new company syncs to Linear as a customer, before any thread is linked.
Comments - internal comments sync both ways, and the customer conversation is mirrored into a pinned comment you can reply to. See "Comments and conversation sync" below.
From Linear into Productlane:
Customer requests - requests attached to a Linear issue appear on the linked Productlane thread.
Public roadmap - your roadmap mirrors your Linear projects and their statuses.
From Productlane into Linear:
Thread backlinks - linking a thread to an issue adds an attachment on the Linear issue that points back to the conversation, with the sender, origin, and title.
When a thread is linked to a Linear issue, Productlane keeps the conversation visible in both places. The anchor comment, titled "Productlane thread connected", and replying from Linear both need Reply to customers from Linear, turned on in Productlane's own Linear settings under Settings → Integrations → Linear, not inside Linear itself. Turn that setting off there to stop the "Productlane thread connected" comment from being posted on linked issues at all, which is the way to keep your Linear inbox from filling up with Productlane comments. With it off, replying to that comment in Linear no longer sends a message to the customer, since the anchor comment is what enables that reply path. Other parts of the Linear connection, like changelog generation from completed projects, keep working either way.
Internal comments sync both ways. A comment or reply added on a thread in Productlane is posted as a comment on the linked Linear issue, and a comment added on that issue in Linear appears back on the thread. Edits and deletes sync too, including replies.
The customer conversation is mirrored into a pinned anchor comment. As soon as a thread is linked to an issue, Productlane posts an anchor comment on the issue linking back to the thread, backfills it with the existing conversation, then adds every new message (email, Slack, live chat, Productlane Agent replies, and Microsoft Teams) under it as it happens, so the full conversation is readable from Linear.
Attachments are mirrored too. Images and files sent or received on the thread are added to the mirrored message: images are embedded inline in the Linear comment, and other files appear as links.
Replying to the anchor comment in Linear sends the reply to the customer through the thread's original channel, exactly as if you replied from the Productlane inbox. The reply includes the same quoted conversation history and email signature a manual reply from the inbox would include. Replies to any other comment on the issue stay internal in Productlane and are never sent to the customer.
Sending requires a Productlane seat that is not Viewer. Viewers, and Linear users with no matching Productlane account, get a warning reply and their message is not sent. If sending fails (for example, a suppressed email address), Productlane posts a warning reply under the anchor explaining why.
If a thread is linked to more than one Linear issue, the conversation is mirrored to each linked issue's anchor comment.
If the anchor comment becomes stale (for example, the thread's linked issue changed), Productlane automatically rebuilds the anchor on the current issue the next time a message needs to be mirrored.
When a project or issue is deleted in Linear, Productlane does not permanently remove it. Instead, it is moved to the Closed status and appears in the Closed section on your roadmap. If someone deletes a Linear project or issue by mistake, its linked threads and customer requests stay visible in Productlane.
To permanently remove a closed project or issue, delete it directly inside Productlane.
Link any thread to an existing Linear issue or project, or create a new one from the thread. Productlane records it as a customer request on the issue, along with the feedback and the contact. The picker hides completed projects and duplicate issues until you search for them by name, and lists projects with the most recently updated ones first.
Turn on Auto-create issues to file a Linear issue for every new thread from your customer channels: the widget, live chat, email, the portal, Slack Connect, Teams, Zapier, and the API. Threads closed by an auto-reply are skipped. New issues start in your default team's triage state.
Apply one of your Linear issue templates when you create an issue from Productlane. See Linear issue templates.
Auto-assign to customer owner - route a thread to the workspace member who owns the Linear customer.
Auto-assign Productlane Agent to bugs - under Settings > AI > Productlane Agent, sends bugs to your Cursor agent so a fix can start before you reply. See Cursor.
Changelog drafts - completing a project in Linear can generate a changelog draft automatically, ready for you to review and publish.
When you connect Productlane, Linear shows the prompt "Read access to your workspace". Here is exactly what that covers and why each part is needed.
Object | Fields used |
|---|---|
Issues | Title, description, status, priority, assignee, due date, labels, attachments |
Projects | Name, description, status, team, icon, color |
Customers | Name, revenue, tier, size, status, domains |
Teams | Name, identifier, states, labels, members |
States | Name, type, for mapping issue status |
Labels | Name, color, for display and filtering |
Members | Name, avatar, for assignee display and auto-assignment |
Productlane reads no billing data, and nothing outside the teams you select.
If you choose Only select teams during setup, Productlane syncs only those teams. Issues, projects, states, labels, and members from teams you did not select are never fetched.
If you choose All teams, every public team in your Linear workspace is included. Private teams are excluded regardless of this setting.
In addition to reading, Productlane writes back to Linear in these ways:
Attachments - adds a backlink on an issue when you link a thread to it.
Issues and projects - creates or updates issues and projects when you act from Productlane (for example, creating an issue from a thread or syncing a status change).
Comments - posts, updates, and deletes comments on an issue to keep internal comments and the mirrored conversation in sync (see "Comments and conversation sync" above).
