Use tags and custom fields
Tags and custom fields add structure to feedback without making the public board feel heavy.
Tags vs fields
Use tags for visible categories customers understand, such as Billing, Mobile, Integrations, or Reporting.
Use custom fields for owner planning context, such as Priority, Customer type, Plan, Effort, or Revenue impact.
Step-by-step
- 1
Create only useful labels. Add a tag or field only when it changes how you filter, compare, or decide.
- 2
Apply tags during triage. Do it while the request is fresh instead of backfilling later.
- 3
Use fields for planning. Fields should support internal decisions without cluttering the public board.
- 4
Filter before bulk action. Narrow the queue by status, tag, or field before changing several posts.
- 5
Clean old metadata. Merge overlapping tags and remove fields that no longer guide decisions.
Details to remember
- Too many tags make the board harder to scan.
- Custom fields should be team-only unless there is a strong customer reason to show them.
- A short metadata system is easier to maintain than a perfect taxonomy.