Manage requests and decisions
Updated 13 Nov 2026
Every request your users send lands in the product's request list. This article explains how to review requests, record decisions, and keep users in the loop.
The request list
Open a product from Your products to see its requests, with vote counts and statuses. Votes from the widget, the portal, the API and your team all count toward the same total, and each person counts once.
Statuses
| Status | Meaning |
|---|---|
| New | Just arrived; nobody has looked yet. |
| Under review | Your team is considering it. |
| Planned | You've decided to build it. It appears on the roadmap. |
| In progress | Someone is building it. |
| Shipped | It's live. Users who asked for it can see it's done. |
| Declined | You've decided not to build it, for now. |
Change a status from the Status box on the request's page and choose Set.
Record a decision
Users trust a feedback board when they can see why things happen. In the Decide box, pick an outcome (Planned, Declined or Later), write a public reason, and choose Record decision.
- The public reason appears on the portal under From the team or Why not now. Write it for your users.
- Every decision is kept in the request's Decisions history, so you can see who decided what, and when.
Internal notes and public replies
- Internal notes are only visible to your team. Use them for context such as which customers asked, or effort estimates.
- Reply publicly adds a comment on the portal, labelled as your team.
Merge duplicates
When two requests ask for the same thing, open the duplicate, enter the other request's number under Merge into request # and choose Merge. Its votes move to the target request, and anyone who opens the old one is sent to the new one. Merging can't be undone.