A feature request board gives your visitors a place to submit ideas and vote on what matters most to them. You manage the backlog in a kanban view and move requests through columns as work progresses. This article walks you through the setup.
You probably already have one
Yaplet creates a feature request board when you sign up, along with a submission form for it. In an English account it is called Feature Requests; in a Hungarian one, Funkciókérések. It arrives with four columns — Under Review, Planned, Closed and Released — and with Planned and Released already public. Look under Communications → Tickets in the sidebar before you build a second one; you may only need steps 2 and 5 below.
1. Create the board
- In the sidebar, under Communications → Tickets, click ＋ New board — the last row of that list. You need the Board management right to see it.
- Yaplet creates the board and drops you on its Settings tab. Set the Name — this one is internal, for your team.
- Change Type to Feature Request and click Save. A new board starts as Custom, and only a Feature Request board can be voted on or shared publicly.
2. Configure your columns
A board you made yourself starts with a single column called New. Open the board from its sidebar row and use Add Column at the top right to add more, up to a generous ceiling you are unlikely to reach. Each column header's three-dot menu renames it, changes its colour, moves it left or right, makes it public or private, archives or deletes all its tickets, or deletes the column.
Columns that work well on a feature board:
- Under review — new submissions nobody has assessed yet.
- Planned — confirmed for a future release.
- In progress — actively being built.
- Shipped — done.
- Won't do — acknowledged but out of scope. Keep this one private if you would rather not publish your rejections.
3. Set column visibility
Public columns appear on your public roadmap page and in the widget's roadmap tab, so visitors can see what stage a request is at. Private columns are team-only. Switch a column with Make Public / Make Private in its three-dot menu; the eye icon in the header tells you which it currently is, and this setting only matters on a Feature Request board.
The first column — the one new submissions land in — is locked. Its visibility toggle is disabled and it cannot be deleted or moved, so unreviewed submissions can never leak onto your public roadmap by accident.
4. Add a submission form
Feature requests arrive through a form, and a form lives on the board it feeds. Open the board's Forms tab and click Add form — the builder opens on a new form already attached to this board. You need the Forms right to see that tab.
Two fields are usually enough:
- A Short text field, marked required, for the one-line summary.
- A Long text field, optional, for detail and context.
The form Yaplet creates at signup already has exactly those two.
5. Show it in your chat widget
Open Brand → (your brand) → Chat widget, go to the Features tab and find the Roadmap section. Pick this board under Roadmap Board, give the tab a Menu Title if you want something other than "Roadmap", and switch Show on Navbar on. Save.
The dropdown only lists Feature Request boards, so if yours is missing, its type is still Custom — go back to step 1. And this is the only picker left on that tab: which AI answers, which knowledge base and which documentation are the brand's business now, so nothing else here needs wiring up.
Import one instead
If your backlog already lives in Trello, Canny or a spreadsheet, bring it across rather than retyping it — and you can duplicate a board you already like. See Moving boards in and out of Yaplet. One thing to expect: an imported board always arrives as type Custom, so switch it to Feature Request on its Settings tab before you try to share it.
With the board set up, publish the public page — see Publish a public roadmap. To understand boards in depth, see Boards explained.