Create a board
Boards group related feedback. A focused board helps customers find existing requests and helps owners triage without noise.
When to add a board
Create a board when the request type or audience is meaningfully different. Feature Requests, Bugs, Integrations, and Mobile can be good boards if each receives enough feedback to stand alone.
Avoid creating boards just to mirror internal teams. Customers think in problems and outcomes, not internal ownership.
Step-by-step
- 1
Choose the board name. Use a plain name customers understand immediately.
- 2
Write the description. Tell users what belongs here and what detail helps your team act.
- 3
Set visibility. Use public for product feedback and private only when the feedback should be gated.
- 4
Add a template if needed. Templates are useful when every request needs the same structured context.
- 5
Archive old boards. Archive instead of deleting when history should remain available internally.
Details to remember
- One strong board is better than five sparse boards.
- Board names should describe the customer input, not the internal team.
- Descriptions reduce low-quality submissions more than strict rules do.