Use tags to group related feedback and internal notes to preserve context for your team.

Add useful context

Open the feedback post. Apply relevant tags using the available tag control. Keep tag names consistent so similar requests can be found together.

Use an internal note for team-only discussion. Check the composer mode before sending so internal context is not posted as a public comment.

Keep status and tags separate

Status records the request's workflow state. Tags describe themes or other categories. Avoid creating tags that duplicate every status.

Connect feedback to a roadmap

Current roadmap views use configured columns and filters over feedback fields. Review those rules to determine whether the post appears.

Do not rely on the legacy instructions for creating and bulk-linking separate Roadmap Topics. After changing feedback or roadmap rules, open the roadmap and verify the resulting cards.

Was this helpful?