Skip to content

Roadmap and changelog · 5 min read

Set up and publish a roadmap

Columns from statuses, what is public, and keeping it current.

The roadmap is a view, not a second tool

The roadmap is built from post statuses. Move a post to Planned and it appears on the roadmap; move it to In progress and then Complete and it moves across. There is no separate list to keep in sync.

The public roadmap has three columns, Planned, In progress and Complete, and visitors can switch between a board view and a list view and filter by board. Posts on private boards never appear on the public roadmap; your team sees them on the admin Roadmap.

What visitors see

Each card shows the post's title, its board and its vote count, and opens the post. Visitors can search titles with Search roadmap, narrow the page with the Board filter, and copy the roadmap's address with Share. The page updates on its own when a post's status changes.

Within a column, posts you have placed by dragging on the admin Roadmap come first, in that order, and the rest follow by votes. Merged posts and posts on archived or private boards are left out. The page loads at most 500 posts across its columns, placed posts first and then the most voted, so a long history in Complete can push less-voted planned work off the page.

Working the roadmap as a team

In the admin area, Roadmap shows the same posts plus an Under review column, so the team sees what is being considered before it is public. Drag a card between columns to change its status; followers are told about the change. Filter by board, or by Assigned to me, to see one person's work.

Moving and ordering cards

Drag a card up or down within a column to set its place; the public roadmap and the embed use the same order. Reordering within a column does not change the status, so nobody is notified. With a keyboard, focus a card and use Space and the arrow keys.

Auto-comment on status change, at the top of the page, is ticked by default. While it is ticked, moving a card to another column also adds a public comment recording the change. Unticking it only drops the comment: followers are still told about the new status.

Only people with Triage feedback can drag cards and see that checkbox. The Owner filter narrows the board to Assigned to me, Unassigned or one teammate's posts.

Choose labels you can honour

Columns are statuses, so you shape the roadmap by renaming and hiding statuses on the Statuses page: you can change each label and colour, and a hidden status is removed from the public roadmap. You cannot add extra columns.

Sequence ages better than dates. If you prefer Now, Next and Later, rename In progress to Now and Planned to Next, and keep anything further out in Under review. Looph has no date or quarter fields, so the roadmap never promises a delivery date unless you write one into a post.

What hiding a status does

On the Statuses page each status has a Visible or Hidden switch, applied when you choose Save changes; Reset puts every name, colour and switch back to the default, again once you save. Hiding a status removes its column from the public roadmap and takes it out of status pickers and filters, while your team's Roadmap keeps every column. It does not hide the posts: posts already in that status keep it and still show its label. Open cannot be hidden, because every new post starts there.

If all three roadmap statuses are hidden, the public roadmap says "This workspace isn't showing any roadmap columns right now." Changing statuses needs the Tags permission and works on every plan, including Free.

Control what is public

What appears on the public roadmap is decided by the board a post is on. Posts on public boards are visible to anyone. Posts on private boards stay off the public roadmap altogether, even for people on that board's allowlist, and your team sees them on the admin Roadmap. Keep competitive or sensitive work on a private board, or in Under review, until you are ready to show it.

  1. 1Open the Statuses page in admin and set the labels and colours for Planned, In progress and Complete.
  2. 2Hide any status you do not want customers to see.
  3. 3Move the posts you have committed to into Planned.
  4. 4Share the roadmap link from your app's help menu, or use Embed roadmap to place it on your site.

Embed the roadmap on your site

Embed roadmap, the code icon at the top of the admin Roadmap, builds a snippet for your own site. Choose a Theme (Auto (match visitor), Light or Dark), an Accent color, a Height between 300 and 900 pixels and whether to Hide top header bar, then copy the Iframe embed or the Direct link. The embed is read-only, and choosing a post opens it on your board in a new tab.

SEO & sharing, the globe icon beside it, sets the public roadmap's SEO title, Meta description and Social image, and has Hide from search engines, which keeps the page out of search results and your sitemap. Only people who can change workspace settings see it.

Keeping it current

Because columns are statuses, the roadmap updates itself as the team works. Moving a post notifies its followers, and publishing a changelog entry can mark the posts it ships as Complete in the same step. From Starter up, a post linked to a Jira or GitHub issue also moves on its own as the issue progresses; the Jira and GitHub integration pages give the setup.

Dates are optional, and rarer than they look: of the twelve public roadmaps we reviewed on 20 September 2026, only Atlassian's and Microsoft's put a target date on items. If you publish dates, state plainly that the roadmap is not a promise to deliver by any date.