Skip to content
rev0Docs

Organize the board

Once a few dozen tickets are on the board, the default columns stop being enough. This page shows how to change the view, keep columns tidy, act on many cards at once, find any ticket, and split your work across several boards.

  1. In the header, click Board (or press 1) while you are already on the board.
  2. Under Board view, pick a view:
    • Board: the columns, from Backlog to Done. A ticket an agent drops is listed with the archived ones: turn on Show archived to see it.
    • List: one collapsible section per column, with compact rows.
    • Table: sortable columns (ID, Title, Status, Priority, Type, Assignee, Tags, Updated). Click a header to sort; a row’s status menu moves the ticket.
    • Calendar: a month grid of tickets by the day they were created. A Loop shows as a bar up to its next run.
    • Timeline: one lane per column on a time axis, with Zoom in, Zoom out and Fit to width.

Result: the board shows that view, and remembers it for this board. Selecting cards and acting on them works the same in every view.

Each column header has two small buttons.

  1. Click Sort cards and pick Manual, Creation date, Modified date, Type (loops first), Priority, Title (A→Z) or Ticket ID. Pick it again to switch between Ascending and Descending.
  2. Click Group cards and pick Tags or Parent. No grouping undoes it.

Result: the column sorts or groups its cards on this device. Grouped by Parent, subtickets gather under their parent; grouped by Tags, a card with two tags shows under both. Expand all and Collapse all in the same menu fold the groups.

A card group is a named, coloured box around cards you choose, to keep related work together in one column.

  1. Select two or more cards in the same column (see Select many cards).
  2. Click Actions, then Group 2 cards.
  3. Type a name for the group and press Enter.

Result: the cards sit in one box you can collapse. Click the group’s name to rename it, change its Group color, or Ungroup it. Groups are saved on the board, so they show on every device.

  1. Hold Cmd (macOS) or Ctrl, or Shift, and click each card. You can also drag across empty board space to draw a selection box, or long press a card on a phone.
  2. In the bar at the bottom, click Actions.
  3. Pick an action:
    • Move to a column (moving tickets out of In Progress asks to interrupt their agents first).
    • Merge all to merge every selected branch that is ready.
    • Group or Ungroup the cards.
    • Archive all or Unarchive all.
    • Delete all, which cannot be undone.

Result: the action applies to every selected ticket. Right clicking a card opens the same menu, and Clear selection (or Esc) ends it. Dragging one selected card moves all of them.

  1. Click the search box in the header, or press Cmd+K (Ctrl+K) or /.

  2. Type words from a ticket’s key, title, tags or description, for example AK-12 or login.

  3. Narrow it with filters, written field:value with no space:

    FilterMatches
    status:a column, from its start: status:todo, status:inprog
    priority:a priority, from its start: priority:urg
    tag:any tag containing the text
    type:a ticket type, from its start: type:loop
    assignee:an assignee containing the text
    board:a board’s acronym, or text in its name

Result: matches from every board show under Tickets, with pages under Knowledge and files under Artifacts. Opening a ticket from another board switches to that board.

Each board has its own tickets, its own ticket prefix (such as AK-218) and its own overrides. One board per project keeps each project’s queue, repository and agent rules apart.

  1. At the top left, click the board name (Switch board).
  2. Click New board….
  3. Fill in Name. Ticket acronym is the prefix before each ticket number: leave it blank to derive it from the name.
  4. Pick a Highlight color, so you can tell at a glance which board you are on.
  5. Click Create board.

Result: the new, empty board opens. Switch between boards from the same menu, or with [ and ].

Give a board its own instructions and settings

Section titled “Give a board its own instructions and settings”
  1. Switch to the board, click its name, then Board settings….
  2. In Agent instructions, write guidance appended to every agent run on this board, for example Never mention the agent in branch names or commit messages.
  3. Under Per-board overrides, pick a setting in Add an override… and give it this board’s value, for example Default working directory for the project’s repository.
  4. Under Per-board permissions, click Override for this board to give this board its own Command permissions or Tool & MCP permissions. An override replaces the global list for this board; the two are never merged.
  5. Click Save.

Result: agents on this board follow its instructions, settings and permission lists; every other board keeps the global ones. Inherit removes an override.

A board can hold tickets no agent ever runs: a backlog of ideas, notes, a human to do list.

  1. Open Board settings… for that board.
  2. Clear Agents can run tickets on this board.
  3. Click Save.

Result: the runner never claims a ticket on this board, and the switcher shows it with agents off. Tick the box again to let agents in.

  1. Open the ticket and click … (Ticket actions) in its toolbar.
  2. Point at Move to workspace and pick the board.

Result: the ticket moves, together with its parent and every subticket, so a tree never spans two boards.

In Board settings…, click Delete. It deletes the board and every ticket on it, and cannot be undone. The last board cannot be deleted.