Build a public roadmap

Create roadmaps that fill themselves from post status, board, tags, and ETA, choose status columns or date periods, and control who can see each one.

A public roadmap shows users what's planned, in progress, and done, and it updates itself as post statuses and target dates change. This article explains how roadmaps work, how to create one, the two layouts, and who can see each roadmap.

How roadmaps work

A roadmap is a saved view, not a list you curate by hand. You define a base filter (which statuses, boards, tags, or author segments qualify) and a set of columns. Every post that matches the filter appears in the matching column automatically. There's no "add to roadmap" step.

Note: Posts appear on or leave a roadmap only because their status, board, tags, author, or target date changed. Deleting a roadmap never changes the posts it showed.

Create a roadmap

You can have several roadmaps, for example "Product roadmap" and "API roadmap".

Open Roadmap from the admin sidebar.
Click New roadmap (the + next to Roadmaps).
Fill in the details:
- Name: for example "Product roadmap"
- Layout: Status columns or Date periods
- Description: optional
- Frequency (date periods only): Monthly, Quarterly, or Semiannual
- Visibility: Public, Team only, or Customer segments
Set the Base filter: the Statuses, Boards, Tags, and Author segments a post must match to appear at all.
For a status-columns roadmap, choose the Columns.
Save the roadmap.

Choose a layout

Status columns

Groups posts by status, kanban style. Each column maps to one status. New roadmaps start with the statuses that have the Roadmap toggle on in Settings > Feedback & Roadmaps > Statuses, but you can add, remove, rename, recolor, set an icon for, and reorder columns on each roadmap independently.

Date periods

Groups posts by their target date (ETA) into monthly, quarterly, or semiannual buckets, plus a No ETA bucket for posts without one. Set a post's ETA from its properties panel in Feedback, or by dragging its card between buckets.

Tip: Use status columns for most roadmaps. Date periods work well when your team commits to ship dates and wants users to see a timeline.

Move posts between columns

Dragging a card changes the post itself, not just its place on the roadmap:

On a status columns roadmap, dragging a card to another column changes the post's status.
On a date periods roadmap, dragging a card to another bucket sets the post's ETA, and dropping it on No ETA clears it.

The change shows everywhere that status or ETA appears, including Feedback and your public roadmap.

Tip: Dragging is the fastest way to update several posts in a planning session.

Visibility

Setting	Who can see it
Public	Everyone who visits your portal
Team only	Team members only (shown with a lock icon in the sidebar)
Customer segments	Only visitors in the segments you select under Visible to

Tip: Plan on a team-only roadmap, then publish items by widening a public roadmap's base filter or by switching the roadmap's visibility.

What users see

On a public roadmap, users see each post's title, vote count, board, and target date (if it has one). They don't see internal notes, private comments, or who the post is assigned to.

Edit or delete a roadmap

Hover a roadmap in the sidebar and open its menu:

Edit: change the name, layout, description, base filter, columns, or visibility, then save.
Delete: remove the roadmap after confirming.

Note: Deleting a roadmap removes only the saved view. Posts aren't changed, because roadmap placement comes from their own fields.

Best practices

Keep it current. An outdated roadmap undermines trust. Move shipped items to Complete and tune the base filter so newly planned items appear automatically.
Show meaningful items. Scope the base filter to major features, popular requests, and significant improvements rather than minor tasks.
Be careful with dates. Use status columns unless you're confident in the ETAs, and keep ideas still under consideration in No ETA.
Celebrate completed work. Leave recently completed items up for a while, then narrow the filter to drop old ones.
Explain changes. When plans change, update the status or ETA promptly and comment on affected posts so subscribers know why.
Link to it. Add your roadmap to your app's footer, help menu, or feature request buttons.