Categorize posts with tags

Create portal or internal tags, apply them to posts, and filter feedback by tag across boards and statuses.

Tags let you slice feedback any way you need, across boards and statuses: which requests affect mobile, which come from enterprise customers, which touch billing. This article covers creating tags, applying them to posts, and filtering by them.

Overview

Manage tags in Settings > Feedback & Roadmaps > Tags. Each tag has a name, a color, a visibility, and an optional description. Tags show as colored badges in the feedback list, on posts, and (for portal tags) on your public portal.

How tags compare with boards and statuses:

	Tags	Boards	Statuses
Several per post	Yes	No	No
Describes a workflow stage	No	No	Yes
Describes the type of content	No	Yes	No

Manage tags

Create a tag

Go to Settings > Feedback & Roadmaps > Tags.
Click New tag.
Enter a Name and pick a color.
Choose a Visibility:
- Portal: shown on the public portal
- Internal: hidden from the portal, visible to your team only
Optionally add a Description explaining when to use the tag.
Click Create tag.

Edit a tag

Open the tag's menu and choose Edit to change its name, color, visibility, or description. Click the color dot to change just the color. Changes apply to every post using the tag.

Delete a tag

Open the tag's menu and choose Delete, then confirm.

Warning: Deleting a tag removes it from every post it's applied to. This cannot be undone.

Apply tags

Open a post from Feedback.
In the properties panel, click Add next to Tags.
Select a tag.

To remove a tag, click the X on its badge.

Filter by tags

In Feedback, select tags in the Tags section of the filter sidebar, or add a Tag filter with the Filter button. Tags combine with every other filter, for example board + tag, status + tag, or a search + tag.

Example tag sets

By platform: mobile, web, desktop, api
By customer type: enterprise, startup, free-tier, beta-users
By priority: high-priority, quick-win, blocking, nice-to-have
By product area: auth, billing, dashboard, reports, integrations
By team: eng-backend, eng-frontend, design, product

Best practices

Start small. Begin with 5-10 tags and add more as patterns emerge.
Name consistently. Short, lowercase, hyphenated names are easy to scan.
Avoid overlap. Use boards for content type, statuses for workflow stage, and tags for everything that cuts across them.
Use Internal tags for team-only labels such as priority or owning team.