Feature Requests

Overview

The roadmap page (/s) shows one of your feature-request boards as a kanban board. Each column is a stage in your pipeline — Planned, In progress, Shipped, whatever you have named them — and visitors can read tickets and vote to influence what you build next.

Kanban board

Columns side by side on desktop, stacked on phones, showing each stage of development.

Upvoting

Visitors upvote what they want, so you prioritise on real demand instead of guesswork.

Ticket details

Clicking a ticket opens a slide-over panel with the full request and an upvote button.

Getting a board onto the public roadmap

Three things have to line up before anything appears at /s:

The board's type is Feature Request

Open the board under Communications → Tickets, go to its Settings tab and set Type to Feature Request. A board created from scratch, and any board brought in through import, arrives as Custom — a Custom board never appears on a public roadmap. The Settings tab is only visible to members who hold the Board management right.

The chat widget points at that board

The board the roadmap shows is chosen at Brand → Chat widget → Features → Roadmap. Boards belong to the organisation, so the widget picks which one to publish.

At least one column is public

New columns are private, so an untouched board shows nothing. See Which columns visitors see below.

Board type, columns and the rest of a board's setup are covered in Board settings.

Board layout

The page opens with the board's own name as its heading, a short line inviting people to vote, and two counters — how many ideas are on the board and how many upvotes they have collected between them.

Below that come the columns. Each one shows:

Its name, with a coloured accent taken from the column's colour
A count of the tickets in it
Its tickets, most-upvoted first

Columns sit side by side and scroll horizontally on desktop, and stack vertically on phones. A column with nothing in it says so rather than appearing broken. The search box in the header filters tickets by title and description across every column at once.

Ticket cards

Each card shows:

An upvote button with the current count
The title — the short, personal-data-free summary of the request
A description preview, trimmed to two lines
The date the request was submitted, under the preview

Ticket details

Clicking a ticket opens a slide-over panel with:

The upvote button and count
The title and the date the request was submitted
The full description, or a note that none was given

The visitor's raw form answers are never shown on the public roadmap — only the ticket's own title and description are published. The answers stay private in your dashboard.

Upvoting

Any visitor can upvote a feature request. The flow is:

Click the upvote button

On a card or in the detail panel.

Give an email address (first time only)

A small dialog asks for it, explaining that it is how you let them know when the feature ships. The address is kept in a cookie in their browser for 7 days, so they are not asked again while voting on other tickets.

The vote is registered

The count updates straight away. Clicking again removes the vote.

The email serves two purposes: it stops the same person voting twice on a ticket, and it gives you a list of people to notify when the feature is released.

Which columns visitors see

Column visibility is set on the board itself, not on the Settings tab. Open the board under Communications → Tickets, use a column's own menu and choose Make Public or Make Private. Public columns appear on the roadmap; private ones stay internal.

Two things to know:

New columns are created private, so you decide deliberately what becomes visible.
The board's first, default column can never be made public — the column new tickets land in stays internal by design.

This is what lets you run one board with every stage on it while showing customers only the part of it that is ready to be seen.