Static docs page
A docs page is easy to publish, but every status change becomes manual upkeep.
Linear public roadmapHow to Create a Public Roadmap with Linear
Use Feedvote as the public roadmap layer for selected Linear work, so customers can follow progress without seeing your internal planning.
200+ teams use Feedvote
Feedvote + Linear
- Publish selected work
- Map statuses to roadmap columns
- Keep private Linear issues hidden
- Update customers as work ships
Quick answer
The simplest path is to keep Linear internal and publish through Feedvote
Create the work in Linear, connect Feedvote, then choose the teams, issues, projects, and labels that belong in the customer-facing view. Map internal states to clear roadmap columns, set public or customer-specific visibility, and let Feedvote keep the shared roadmap current while Linear remains your private planning system.
step 1
Choose the Linear work customers should see
Feedvote's import wizard turns a large Linear workspace into a deliberate publishing source. Choose the content and preview the scope before records are created.
- Import issues, projects, or a combined roadmap
- Select source teams and filter by projects, issue labels, or project labels
- Set one created-date condition, completed-work handling, and comment rules
step 2
Set public and customer-specific visibility
A roadmap can be broadly public without making every item public. Feedvote separates anonymous public visibility from named customer-group access.
- Use a public-board label filter for anonymous visitors
- Assign selected work to customer groups manually
- Automate issue and project access with separate Linear label rules
step 3
Map Linear progress to public roadmap columns
Turn internal delivery status into simple customer-facing labels like planned, in progress, and shipped.
- Use plain-language roadmap stages
- Avoid exposing engineering-only workflow details
- Keep the public roadmap current as Linear changes
step 4
Publish the roadmap on a clean public page
Give customers, prospects, and stakeholders a place to check progress before they ask your team for a status update.
- Share a public roadmap link in your app, docs, or help center
- Use branded pages instead of exposing internal tools
- Show roadmap progress next to related feedback
step 5
Announce shipped Linear work to customers
When a roadmap item ships, Feedvote helps turn that progress into updates customers can actually read.
- Notify voters when linked work moves forward
- Publish customer-friendly changelog posts
- Reduce repeat questions about roadmap status
Why Feedvote
Feedvote vs a static Linear roadmap workaround
Docs pages and spreadsheets can show a roadmap snapshot. Feedvote keeps the roadmap connected to customer requests and Linear progress.
Spreadsheet roadmap
A spreadsheet works internally, but it is not built for customer votes, notifications, or a polished public board.
Public issue tracker
An issue tracker can expose too much implementation detail and can be hard for non-technical customers to scan.
Feedvote publishes the customer-facing version
- Connect roadmap items to customer feedback
- Show simple public statuses instead of internal workflows
- Keep Linear as your private execution system
- Notify customers when public roadmap items change
Linear resources
More ways to connect Feedvote and Linear
Linear Public Roadmap & Customer Feedback Portal
See the full Feedvote workflow for Linear feedback, feature requests, and public roadmap updates.
Linear Client Portal for Agencies and SaaS Teams
Give each client a controlled view of selected Linear work, requests, and progress without sharing your workspace.
How to Collect Customer Feedback for Linear
Turn raw customer ideas into prioritized Linear issues without filling Linear with noise.
Feature Request Board for Linear Teams
Give users a place to submit, vote, and follow requests while engineering stays in Linear.
Canny Alternative for Linear Teams
Compare Feedvote for Linear-first teams that want feedback, roadmap, and updates together.
Customer-Specific Roadmap Visibility
Give every customer group a controlled view of selected Linear issues and projects.
Linear Import Filters
Choose source teams, projects, labels, one created-date condition, completed-work handling, comments, and status mapping before import.
Public Portal Access Settings
Control browsing, participation, moderation, public labels, displayed fields, and navigation.
Common questions
Linear feedback and roadmap FAQ
Can I make a Linear roadmap public?
Yes. Feedvote gives Linear teams a public roadmap layer so selected work can be shared with customers while private Linear work stays internal.
Should every Linear issue appear on a public roadmap?
No. Most teams publish only customer-relevant work. Feedvote helps you keep private work hidden and show the roadmap items that matter externally.
Can Feedvote show planned and shipped work?
Yes. Feedvote can show customer-facing roadmap stages such as planned, in progress, and shipped.
Do customers need Linear accounts?
No. Customers can view the roadmap and follow updates in Feedvote without access to your Linear workspace.
Can I filter which Linear issues and projects are imported?
Yes. Choose source teams, issues, projects, Linear projects, issue labels, project labels, dates, completed work, and comment behavior before previewing the import.
Can different customers see different roadmap items?
Yes. Customer groups can receive manual item access or automatic access to matching Linear issues and projects based on separate label rules.
Build a Linear roadmap customers can follow.
Choose what to publish, keep internal work private, and close the loop when customer-requested work ships.