Triage Feedback

Once feedback starts coming in, the quality of your workflow matters more than the volume.

Boarbs gives you a lightweight triage flow so requests move from raw input to clear decisions.

Start With Inbox

For most teams, the default Inbox status is the daily starting point.

Use it for new requests that still need review.

Your basic workflow can look like this:

1. review new posts in Inbox
2. decide whether they belong in Planned, In Progress, or Canceled
3. use Spam for unrelated or promotional posts that should not sit under Canceled
4. assign owners where helpful
5. set an ETA when timing becomes clear

Filter and Sort What You See

In the board view, you can narrow the list using:

• search
• status filters
• tag filters
• assignee filters
• sort order (mostVoted, newest, oldest)

By default, All Requests shows the newest requests first and hides canceled and completed requests; use the status and sort filters to include those statuses or choose another order.

This makes it easier to review the right slice of feedback instead of scanning the whole board every time.

Use the Post Detail View for Decisions

Open a post to manage the important details:

• change the status
• assign an owner
• set or clear an ETA
• mark unrelated posts as spam
• review votes and comments
• add private team notes

This is the fastest way to turn vague customer feedback into an actionable item.

On a phone or a tablet narrower than the large breakpoint, that page is one column: title, body, and comments first, then status, board, assignee, ETA, and the rest of the details underneath. The two-column desktop layout is unchanged.

Add Images to a Post

When creating or editing a post, select Attach in the editor to upload an image as an attachment.

To place an image directly in the post text, copy the image, click where it should appear in the editor, and press Ctrl+V. Attached and pasted images appear on the post after you create or save it.

Keep Internal Context Private

Use Team Notes when your team needs internal context that should not be shown publicly.

That is useful for:

• implementation concerns
• duplicate tracking
• internal decision rationale
• coordination between product and engineering

Use Bulk Actions for Cleanup

When several posts need the same change, use bulk actions to:

• move multiple posts to a new status
• delete multiple posts
• merge duplicates

When posts are merged, the primary post stays, while votes, comments, and tags from the other posts are combined into it.

A Simple Weekly Triage Routine

Here is a practical cadence for small teams:

Daily or every few days

• clear Inbox
• assign obvious owners
• merge obvious duplicates

Weekly

• review top-voted requests
• move realistic items into Planned
• update ETAs where confidence exists
• refresh the roadmap

Monthly

• archive or cancel stale requests
• review whether your statuses and boards still fit the workflow

What Not to Do

• do not create too many statuses too early
• do not assign ETAs before your team has real confidence
• do not let duplicates pile up in Inbox
• do not leave the roadmap stale once customers start relying on it

Next Steps

• Merge Duplicate Posts — Preserve votes and discussion while consolidating repeated requests
• Connect Linear — Link triaged posts to Linear issues and synchronize their statuses
• Plan Your Roadmap — Turn triaged requests into a clear roadmap
• Create Boards — Split workflows only when one board is no longer enough