> ## 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.

# Signals Tab

> The default Triage view — review tracked items one at a time, then promote, attach, merge, or dismiss

The Signals tab is the default Triage view. It lists every tracked item with `in_triage: true`. Use it to clear your inbox — for each item, decide whether it deserves project work, belongs to an existing project, is a duplicate, or shouldn't be tracked at all.

## The List

The left pane shows tracked items as a sortable list. Each row carries:

* **Title** — user-entered or auto-generated
* **Type** — colored pill (Bug, Feature Request, etc.)
* **Status** — current state
* **Extraction count** — how many signals are linked
* **Triage reason** — why it entered triage (e.g., "high urgency")
* **Urgency** — numeric level (1–5)

### Sort and Filter

* **Sort:** active (default), newest, signals count, priority (urgency)
* **Filter:** type, status, assigned to me, has/no ticket
* **Search:** matches title, status, triage reason, type, ticket ID

### Empty State

When the queue is clear, you'll see: **"Triage is clear."** Use that as a cue to look at Decisions or Clusters next.

## The Detail Pane

Click any row to open it in the right pane. The detail shows:

* **Metadata** — title, description, type, status, urgency
* **Evidence** — extraction cards for every linked signal: call summary, feedback excerpt, person, company, date
* **Actions bar** at the bottom

## Inline Field Edits

Three dropdowns in the detail header let you update fields without leaving the page:

| Dropdown     | What It Sets                                                                       |
| ------------ | ---------------------------------------------------------------------------------- |
| **Type**     | The item's tracked-item type. Updates are written via the same API used elsewhere. |
| **Status**   | Current state (Open, In Progress, Done, etc.). Custom statuses respected.          |
| **Assignee** | The team member responsible. Click your name to toggle assignment to yourself.     |

## Actions

All actions are in the detail-pane footer.

### Promote to Project

The most common path. Sets `status: in_progress`, `in_triage: false` — the item moves to `/projects` and disappears from this list. Requires the `projects` flag.

### Attach Signals to an Existing Project

If the item belongs to an active project, attach its signals there instead of creating a new one. Opens a project picker; signals attach in the "suggested" review state. Requires the `projects` flag.

### Create / View Ticket

Push the tracked item to Linear as a new issue. The modal builds a markdown description from the item plus its linked signals; you can edit the title before pushing. If a ticket is already attached, the button changes to **View ticket** with a link out.

### Merge Duplicate

Opens the [Merge Duplicate](./promote-and-merge#merge-duplicates) flow — finds similar items and lets you merge the current one into a target.

### Correct Classification

Submits feedback that the item was mislabeled. Options:

* **Wrong type** — pick the correct type
* **Should not be tracked** — flag as a false positive

The reason field is optional but useful. The system learns from corrections over time.

### Launch Investigation

Kicks off a Signals Background Agent run that auto-analyzes the item, looks for related signals, and suggests actions. You pick the question (free text) and the action policy:

* **Suggest only** — the agent surfaces suggestions for human review
* **Approval required** — the agent can act after approval at each step

The run shows up in the AI Chat surface; polling and approval happen there.

### AI Route

Opens the [AI Routing](./ai-routing) modal — the system proposes the best home for the item (attach or create) with a confidence score and editable fields.

## Bulk Actions

Hold shift or click checkboxes to select multiple items. With the `projects` flag on, **Promote N** in the footer bulk-promotes the selection through a bounded-concurrency queue. A toast reports how many moved successfully and breaks down any failures.

<Tip>
  Use the **Correct → Should not be tracked** option liberally. The classifier improves the more you tell it what doesn't belong here.
</Tip>