Board
The Board is the central workspace for your tickets. It shows every ticket in one of four stage columns and shows whose turn it is: yours, or Clears'. Cards move between the columns as Clears triages, builds and hands work back to you for review.

Stage columns
| Column | Subtitle | What it holds |
|---|---|---|
| Prepare | Triage, questions, cycle, breakdown | Tickets being triaged, waiting on questions, or being broken down |
| Build | Clears implements, opens PRs, self-reviews | Tickets Clears is implementing |
| Review | You review and merge | Tickets with work ready for you to review |
| Done | Finished and closed | Finished tickets |
Each column header shows a count of its tickets. A long column shows 50 cards and loads more as you scroll. While more cards are waiting, the header reads, for example, "50 of 143".
The Board places a ticket by what Clears knows about it (triage, runs, pull requests and approvals), not by the status in your tracker. The one exception is a ticket that is closed in the tracker: it is in Done. For the statuses themselves, see the story lifecycle.
Whose turn
Every card says whose turn it is:
| State | Meaning |
|---|---|
| Waiting for you | Clears needs something from you, such as answers, an approval or a review |
| Clears working | Clears has a run in progress |
| Queued | A run is waiting to start |
| Failed | A run failed and needs your attention |
| Done | The ticket is finished |
Within a column, cards are ordered by whose turn it is: failed first, then waiting for you, then Clears working, then queued, then the rest. Cards in the same state are ordered by priority, then by last update.
The card
Each card shows:
- Type icon and key - the ticket's type and identifier.
- Dependent badge - the ticket waits on another ticket.
- Title - the ticket's summary.
- Epic chip - the epic the ticket belongs to, if any.
- Status line - what is happening now, with the whose-turn word, such as "Waiting for you".
- Current activity - shown only while Clears is working: what Clears is doing right now. During implementation it includes subtask progress, such as "Subtask 1 of 2 in progress".
- Failure line - on a failed card, a short description of what went wrong.
- Triage block - shown only in Prepare, once triage has a score: readiness as a percentage, plus Complexity and Risk.
- Avatars - the reporter and the assignee.
- Time - how long ago Clears last worked on the ticket, or when it was last updated.
- Action button - the next step, when it is your turn or a run failed.
Action buttons
A button shows only when it is your turn or a run failed. Which one depends on the step the ticket is at:
| Button | When it shows |
|---|---|
| Start Triage | The ticket is waiting for you to start triage |
| Run | Triage is done and the ticket is ready for Clears to implement it |
| Answer questions | Clears has questions for you, from triage or from analysis |
| Review enrichment | Clears has enriched the ticket and it waits for your approval |
| Review breakdown | Clears has proposed a breakdown and it waits for your approval before implementation |
| Review PR / Review PRs | Work is ready for review. Review PR is for one open pull request, Review PRs for more than one |
| Mark as done | The work is delivered and the ticket is waiting for you to close it |
| Fix and retry | A run failed, or triage needs a fix before it can continue |
| See options | Clears does not support the ticket's type as it is, and you need to choose how to proceed |
| Review | A run is live and not waiting on you, or the ticket needs your attention for another reason |
Toolbar
The toolbar sits above the columns.
-
Search - find tickets on the Board.
-
Whose turn - narrow the Board to one state. Choose Everyone, Needs you, Clears working or Failed. Each option shows a count.

-
Epic - pick one or more epics to show only their tickets. Search the list by name or key.

-
Filters - open the filters popover. It has Show only action needed items, which hides tickets that don't need you, and filters for Project, Assignee, Reporter and Type. Under Presets, choose Save current to keep the current combination of filters for later.

-
Sort - order the cards by Ticket ID, Summary, Last updated, Reporter, Assignee or Triage score, in Ascending or Descending order. Without a sort, the Board uses the order described in Whose turn.

-
Time range - limit the Board to tickets updated within a period. The default is Last 30 days.
Adding tickets
Click Add Task in the toolbar. When Jira is connected, it opens a menu with Create new and Import from Jira. Otherwise it opens the create form directly.

Create a task
Create new opens the Create task form:
| Field | Required | Description |
|---|---|---|
| Summary | Yes | A clear title describing what you want built |
| Description | No | Background, context or instructions |
| Images | No | Screenshots, mockups or diagrams |
| Project | When shown | The project the ticket belongs to. Shown when your account has projects, and required when a tracker is connected |
| Parent epic | No | Link the ticket to an existing epic |
| Priority | No | The ticket's priority; it has a default |
On accounts connected to Jira, the form also shows the fields your account has configured for creating tickets.

Click Create Task to create the ticket. Clears then starts triage on it if your account's triage settings allow it. You don't need to add a label.
Import from Jira
Import from Jira opens a dialog listing the tickets in your Jira projects. Search for tickets, select the ones you want and import them. Clears triages each imported ticket and adds it to the Board.

:::tip Writing effective stories The more context you provide, the better the AI performs. Include:
- What the feature should do (user-facing behavior)
- Where it fits in the existing codebase (if you know)
- Any constraints or edge cases to handle
- Screenshots or mockups for UI work :::
Open a ticket
Click a card, its title or its action button to open the ticket panel beside the Board. The exception is Run: it starts the run straight from the card and doesn't open the panel.
Real-time updates
The Board updates live, without a page refresh:
- Stage changes - cards move between the stage columns as Clears triages, builds and hands work back to you.
- Current activity - the Current activity block on a working card updates as Clears moves from step to step.
- Whose turn - status lines, action buttons and counts change as soon as it becomes your turn or a run fails.