
The Feature requests settings page publishes your Linear requests as a public roadmap and controls what customers see there. It makes your Linear requests publicly or privately available.
Settings > Features > Feature requests.
The page lives at /settings/roadmap. Every control saves automatically the moment you change it.
A button in the top right of the header. It opens the Feature requests walkthrough article in the in-app docs viewer.
The card at the top controls the public visibility of your roadmap.
The switch turns publishing on and off. When on, the card title reads "Feature requests are public"; when off, it reads "Make Feature requests public". This maps to your public roadmap link.
Below the switch is a read-only field showing the public URL, in the form yourdomain/request. Click the field to copy the link. Click the arrow icon to open the roadmap in a new tab.
This setting saves automatically. The settings listed below only appear once the roadmap is public.
A card that links to Settings > Portal (/settings/portal). Use it to set up SSO, a custom domain, the portal theme, and a private portal.
A card that links to Settings > Support Portal (/settings/support-portal). Use it to activate the support portal for individual customer portals.
A dropdown, shown only when the roadmap is public. It sets how requests are ordered on the roadmap.
"Linear" orders by your manual Linear order.
"Importance" orders by request count.
The default is Importance. It saves automatically.
A toggle, shown only when the roadmap is public. When on, the roadmap shows the due date of Linear issues and projects. It saves automatically.
A toggle, shown only when the roadmap is public. When on, Linear Initiatives appear on your portal. It saves automatically.
A toggle, shown only when the roadmap is public. When on, each customer sees all requests from their team, including those raised by teammates. It saves automatically.
A toggle, shown only when the roadmap is public. Off by default, so issue descriptions shuse the public description only. When on, issue descriptions whenever no public description is set show the internal Linear description. It saves automatically.
This setting is not limited to the public roadmap: it also controls whether the internal Linear issue description can appear as a fallback in the Customer Support Portal and in the widget's requests list and conversation panel.
This toggle is not limited to the roadmap: it also controls the issue description a contact sees in their Support Portal and widget conversation view. See "What customers see" below for the full behavior.
Feature requests are sourced from Linear, and the roadmap can show a customer-facing version of each request in place of the raw Linear text. Every issue and project has an optional public title and public description that you set from its detail panel in Productlane.
Titles. The roadmap shows the public title whenever one is set. When it is empty, the roadmap falls back to the Linear title. This is true for both issues and projects. The Customer Support Portal and the widget's requests list use the same priority: public title first, falling back to the Linear title or project name.
Issue descriptions. By default, both the roadmap and the Support Portal show only the public description of an issue, and the internal Linear description stays private. Turning on the "Linear issue description" toggle above switches this everywhere it applies: the roadmap and the Support Portal then show the Linear description, falling back to the public description when the Linear description is empty. The Customer Support Portal and widget conversation panel follow the same rule: they show the public description first, and only fall back to the internal Linear description when this toggle is on.
Project descriptions. The roadmap, the Customer Support Portal, and the widget all show the public description of a project when one is set. When it is empty, they fall back to the Linear project description, regardless of the "Linear issue description" toggle (that toggle only gates issue descriptions).
With translations enabled, a matching translation takes priority over both the public and the Linear text.
Go to Settings > Features > Feature requests.
Turn on the "Make Feature requests public" switch to publish your roadmap.
Copy the public roadmap URL from the read-only field, or click the arrow icon to preview it in a new tab.
Set "Sorting" to "Linear" to follow your manual Linear order, or "Importance" to order by request count.
Turn on "Due dates" to show Linear issue and project due dates on the roadmap.
Turn on "Initiatives" to show Linear Initiatives on the portal.
Turn on "Team requests" so customers can see all requests from their team.
Turn on "Linear issue description" to display the Linear issue description on the roadmap, the Support Portal, and the widget and in the Support Portal.
Open "Portal settings" to configure your custom domain, SSO, theme, and private portal.
Sorting, Due dates, Initiatives, Team requests, and Linear issue description only appear after the roadmap is made public. If you do not see them, turn on the publish switch first.
Feature requests are sourced from Linear, so the roadmap reflects your connected Linear workspace.
Every control saves instantly. There is no Save button.
"Team requests" is the same setting exposed on the Support Portal page; changing it in either place affects both.
"Linear issue description" also affects the Customer Support Portal and the widget's requests list and conversation panel, not just the public roadmap.
"Linear issue description" also affects the Support Portal and widget conversation view, even though it lives on this page.