Tag New Submissions

Boarbs supports tags, tag filters, and tag-aware roadmap filters.

What it does not currently provide is a rule engine that automatically tags new submissions based on keywords, forms, or routing rules.

What You Can Do Today

Today, the practical tagging workflow in Boarbs is:

• define your tag set in Settings → Tags
• decide which tags should be public or private
• attach tags when your team creates posts in the app
• apply or clean up tags during triage for incoming feedback
• use tag filters in board, portal, embed, and roadmap views

That is enough for many teams, as long as the tag system stays small and intentional.

Keep Your Tag System Small

Tags work best when they answer a clear question, such as:

• which product area is this about
• what kind of request is this
• should customers see this tag publicly
• does this request belong to a specific theme or initiative

Avoid turning tags into a second board or status system.

Public vs Private Tags

Boarbs tags can be public or private.

Use public tags when they help customers filter or understand the request.

Use private tags when they are only useful for internal routing or review.

Best Workflow for Public Intake

For customer-facing boards, the most reliable pattern is:

1. collect new requests into Inbox
2. review them regularly
3. add tags during the first real triage pass
4. use tags consistently for similar requests
5. merge duplicates before inventing more tags

This gives you cleaner data than trying to over-automate too early.

Where Tagging Is Strong Today

Boarbs already handles tags well in these places:

• filtering internal board views
• filtering public board and embed views
• filtering roadmap content
• attaching tags when your team creates a post in the app

Where Tagging Is Still Limited

Today, Boarbs does not give you a built-in rule-based auto-tagger for incoming submissions.

Tag editing in the post detail workflow is also more limited than the create-post flow, so teams often do their main tag assignment during creation or first review.

If You Need True Auto-Tagging

If feedback first lands somewhere else, the best current path is to import or create posts through the API or CLI with tagIds already assigned.

That is a better fit when:

• you already classify feedback in another system
• you are migrating data in bulk
• you want predictable imports instead of manual cleanup

Recommended Starting Set

For a new workspace, a simple tag system often looks like:

• one set for product areas
• one small set for request types
• private tags for internal routing only

If the list gets long quickly, simplify it before adding more automation.

Next Steps

• Triage Feedback — Apply tags during the first real review pass
• Create Boards — Use boards only when tags and filters are no longer enough
• Import From CSV — Bring in already classified feedback from another tool