Triage (Documentation Index
Fetch the complete documentation index at: https://docs.buildbetter.ai/llms.txt
Use this file to discover all available pages before exploring further.
/triage) is BuildBetter’s product-ops inbox. It’s a unified review queue where teams decide what should become real work — and what shouldn’t. Raw signals, customer asks, clusters, GitHub PRs, and Linear tickets all flow through here, and you decide whether to promote each item to a project, merge it with an existing project, attach it as evidence, dismiss it, or investigate further.
What’s in a Tracked Item
A tracked item is the unit of work in Triage. It’s a de-duped, enriched version of one or more raw signals. Whenin_triage: true, it shows up in the Signals tab. Each item has:
- A title (auto-generated or user-entered)
- A type (Bug, Feature Request, Decision, etc.) — fully customizable per workspace
- A status (Open, In Progress, Done, etc.) — also customizable
- An urgency level (1–5)
- A triage reason (why it landed here — high urgency, auto-flagged, manual)
- Linked signals (the evidence)
in_triage: false and status: in_progress and shows up in Projects.
The Six Tabs
Each tab focuses on a different inbound stream. Click a tab to see counts in the header.Signals
Individual tracked items that need a routing decision. Assign, change type/status, merge duplicates, correct misclassifications, push to Linear, or promote to a project.
Decisions
Project-setup decisions waiting on you — missing scoping, unassigned areas, stale PR reviews, customer asks with no project, unattached calls.
Clusters
Aggregated groups of customer signals from /clusters, embedded here. Promote a whole cluster to a project in one move.
PRs
Open GitHub PRs routed for human review — especially “only Codex has reviewed” PRs. Detect plan files, sync from GitHub, bulk-promote.
Topics
Live, real-time groupings of customer themes from Slack and Intercom. The canonical Topics surface — detail page, manual splits/moves, sources, and the Linear Evidence Tracker all live here.
Tickets
Linear issue browser. Search and filter Linear tickets, then bulk-promote them into BuildBetter projects with the ticket auto-attached.
Cross-Cutting Actions
These actions work on most tracked items, regardless of the tab they came from.- AI Route — let the AI suggest where the item belongs (attach to existing project or create a new one) with editable fields and confidence score.
- Promote — move the item from triage to
/projects(single or bulk). - Merge Duplicate — find similar items and merge the current one into a target.
- Correct classification — tell BuildBetter the item was mislabeled. The system learns.
- Push to Linear — create a Linear issue from the tracked item, with markdown description built from the item + linked signals.
- Launch investigation — kick off a Signals Background Agent run to auto-analyze and suggest actions.
How Items Enter Triage
- Auto — BuildBetter detects high-urgency / high-relevance signals and creates a tracked item with
in_triage: true. - Manual — click New item in the title bar to create a tracked item from scratch.
- Routed — clusters, PRs, and Linear tickets can be brought into the triage flow via their respective tabs.
How Items Leave Triage
- Promote to a project — most common path.
- Merge into an existing item.
- Correct → Skip — mark as “should not be tracked”; learns the classifier.
Feature Flags
- The PRs tab is gated by the
pr_triage_realfeature flag. - Bulk promote (across Signals, PRs, and Tickets tabs) is gated by the
projectsfeature flag. - All other tabs are always visible.