Skip to content

Board reference

This page collects the finer details of each board feature. If you’re new to the board, read Board and Writing tickets first. You can use the board without knowing anything on this page.

  • There are five statuses: Backlog / Todo / Doing / Review / Done, the same as the five Kanban columns
  • Parents and children go two levels deep. A ticket with children gets an EPIC badge and a progress bar showing how many of its children are Done. Grandchildren aren’t allowed
  • A ticket has one assignee, either a person or a minion. Setting one clears the other
  • Only members of the project can be assigned. People and minions removed from the project disappear from the list. Tickets they already hold keep showing them as assignee, so when handing over, filter by assignee and reassign
  • A ticket created without an assignee is assigned to whoever created it (if they’re a project member). To leave it unassigned, clear the assignee afterwards
  • Priority (low / normal / high / urgent) is for display and filtering; it doesn’t set the order of work. The order of cards within a column does
  • The due date on a card changes as the deadline gets close: yellow “{n}d left” from three days before, “Due today” on the day, and red “{n}d overdue” once it has passed
  • To refer to a ticket in chat, use a [task:UUID] tag. Hover over a card to show a button that copies it

Switch between them with the tabs in the header. They show the same tickets for different purposes. Reloading the page brings you back to Kanban.

? Tips, to the right of the tabs, lists the actions you can use in the current view that aren’t visible on screen, such as modifier keys and double-clicks. A dot appears on the button when new ones are added.

ViewUse it to
KanbanSee what’s moving right now and where things are stuck
TableLine up every ticket to compare them, or edit many at once
PlanningChoose which tickets go into a sprint (only when you use sprints)

Five columns. Drag a card to move it between columns, or up and down within one. That order is also the order minions work in.

  • Tickets can only be created on Kanban. Click + in a column header, type a title and press Enter, and the ticket goes into that column
  • The Done column can be collapsed with the ▾ in its header
  • ⚙ Display chooses what cards show (priority, milestone, sprint, subtask count, due date, assignee). It’s saved per project in your browser
  • Rest the cursor on a card for a moment and its family (the epic and its children) lights up
  • Hold Alt (Option on a Mac) and drop a card on another card to make that card its parent. Status and order stay as they are. You can press the key after you start dragging
    • While you hover, the top edge of the card says “Make parent”. Tickets that can’t be parents (child tasks, done tasks), or dragging a ticket that has children, show the reason and won’t accept the drop
    • Undo in the notice that appears for a few seconds afterwards reverses it
    • To remove a parent, use Parent in the ticket’s details. Dropping never removes one

A spreadsheet-like view: one row per ticket, one column per field. Status, priority, due date and custom fields can be edited right in the cell (change the assignee in the details). A Kanban card only has room for a few pieces of information, so this is where you go to compare every field side by side.

  • Click a column header to sort (ascending → descending → off). Turning it off restores the manual order
  • Drag the right edge of a header to resize a column. Widths are remembered per project in your browser. Double-click a column border to reset that column, or use Reset column widths in the toolbar to reset them all
  • The title column stays in place when you scroll sideways
  • Grouping splits rows by status, assignee or an option field. Each group heading shows a count, so you can read off how many tickets are piling up in each bucket
  • Selecting rows brings up a bar for applying one value to all of them. It sets the same custom field value on every selected ticket
  • Export CSV exports with the current filters and order. Formula columns export their calculated values

The view for working with sprints. See Sprints.

The filter bar below the header narrows down which tickets are shown. The same conditions apply to Kanban, Table and Planning (Planning alone ignores sprint conditions).

  • Click + Filter to choose conditions from a menu. Hide Done and Assigned to me, the most common ones, are at the top
  • Each condition appears as a chip. Remove one with its ×, or all of them with Clear all
  • Type straight into the bar to search titles and descriptions. Press Enter and the search words become a chip too
  • The conditions are part of the URL, so sending the link opens the board with the same filters. Your browser also remembers the last conditions you used

You can filter by status, assignee, priority, milestone, sprint, due date, parent (epic) and overdue, plus every custom field.

Give a set of conditions you use often a name. Save it with Views → Save the current filter, and from then on picking it from the list applies the same conditions.

Saved views are shared with everyone who can open the project, and anyone can update or delete them. Only the filter conditions are saved — not the view type or the table’s sort order.

If the conditions include “Me”, they apply to whoever is looking. Make one view for “assigned to me and not Done”, and everyone sees their own work.

When you change the conditions of the view you’re on, the button gets an (edited) badge. Update “(view name)” with the current filter in the menu overwrites it.

You can also type conditions. Once you’re used to it, this is quicker than opening the menu.

-status:done assignee:@me due:<2026-12-01
  • Conditions separated by spaces must all match
  • Commas mean “any of” (status:todo,doing)
  • A leading - means “not”
  • none matches an empty value, * matches any value
KeyExample
status-status:done / status:todo,doing
assigneeassignee:@me / assignee:none
prioritypriority:high,urgent
duedue:<today / due:none
isis:overdue (past due, excluding Done)

You can add your own fields to tickets. The main use is declaring rating fields — “user impact”, “business impact”, “estimate” — and letting a combined score decide the order.

Fields are shared across the workspace and set up from Edit fields in the Table view. A workspace that has not set any up sees nothing — no extra columns, inputs or filters — so the feature stays out of the way when you do not want it.

Values are entered in the table’s cells. They don’t appear in a ticket’s details.

Drag the ⋮⋮ handle to reorder fields. That order is what the table’s columns, the chips on cards and the filter bar all follow.

TypeUsed for
OptionsRatings, categories. This is what a rating field is
NumberEstimates, reach (can carry a unit)
CheckboxYes/no
DateA date other than the due date
TextA one-line note
FormulaA read-only value calculated from other fields

Build rating fields as Options. A number field would work, but options let “3” and “medium” be the same thing, which keeps entry, filtering and grouping straightforward. A new option field starts life with a ready-made 1–5 scale, so naming it is all it takes.

Each option can carry a score — the number a formula reads. Giving options colours makes them readable at a glance on both the board and the table.

Combine axes with a Formula field. Create one called “Priority Point”, pick Sum, tick “user impact” and “business impact”, and it fills itself with their total. Pick Product and it multiplies instead.

A formula column behaves like any other: click its header to sort by score, or show it on cards. The value is never stored — it is calculated every time it is displayed, so changing the weights or the operation reorders every ticket immediately.

Formula columns cannot be edited by hand. If you want to type a value, use a number field.

If any field a formula reads is empty, the formula shows ”—”, not 0. Treating an unrated ticket as worthless would defeat the point of having rating fields at all.

Unrated tickets always sort to the bottom, ascending or descending. To find them, filter that formula field by Not set.

Tick Show on Kanban cards in a field’s settings and it appears as a chip on the board. Fields with no value are left off.

Show too many and the board stops being readable, so keep it to what you need at a glance. The place to see everything is the Table.

A sprint is a way to group tickets together and start them with “go from here”. You can use the board without sprints. You mostly need one when you want minions to pick up tickets on their own.

A sprint has three states: planned → active → completed. Only one sprint can be active per project. A sprint has only a name and an optional goal — no dates. It never ends on its own; it’s completed when someone clicks Complete.

Create a sprint with + Sprint in the Kanban header. A new sprint is planned. There are two ways to add tickets:

  • Choose a sprint under Sprint in the ticket’s details. Both planned and active sprints can be chosen
  • Drag in the Planning view (described below)

Adding a ticket to a sprint doesn’t change its status. Minions only pick up Todo and Doing tickets, so move tickets you’re handing over to Todo.

Two stacked lists: the selected sprint on top, and tickets whose status is Backlog below. If there are several sprints, switch between them in the top section.

  • With a planned sprint (“Next Sprint”) selected, dragging a ticket from the bottom list to the top adds it to the sprint. Use Select to pick several and move them together
  • With the active sprint (“Active Sprint”) selected, you can see its tickets, but can’t drag tickets in or out

▶ Start makes a sprint active. It’s disabled while another sprint is active. To start, every ticket in the sprint must have:

  • an assignee
  • at least one acceptance criterion

If something is missing the sprint will not start, and you are shown exactly which tickets fall short. This gate exists to confirm the sprint is something minions can actually pick up: with no assignee nobody claims the work, and with no acceptance criteria there is no way to tell when it is finished.

This check only runs at start. Tickets added later through Sprint in the details skip it, so check their assignee and acceptance criteria yourself.

Complete lets you choose what happens to tickets that aren’t Done:

  • Return to backlog — takes them out of the sprint and sets their status back to Backlog
  • Carry over to next sprint — moves them to the newest planned sprint. This needs a planned sprint to exist, so create one first

Finished sprints can be looked back on from History. Only planned sprints can be deleted.

You can also cut sprints into fixed periods, such as two weeks: decide in the Planning view which tickets go in, then look back when it ends. Try this once you want to know how much the team gets through in a set period. When you’re starting out, the “keep one started” approach in Handing tickets to minions is all you need.

A milestone marks “what will be finished by when” — a point with a target date, such as “Autumn campaign launch” or “New menu goes on sale”.

The roadmap lays milestones out over time and shows how far along each one is. It’s separate from the board: turn on Roadmap under Features in the project’s Settings tab, and a Roadmap ↗ tab appears on the project. The roadmap screen is currently in English only.

  • Create a milestone with + New milestone. A milestone has a title, description, target date and status; click its name to edit it
  • Link a ticket to a milestone with Milestone in the ticket’s details. Set it on a parent and its children count toward the same milestone
  • Each milestone row shows a bar up to its target date and how many of its tickets are Done. Expand it with ▸ to list its parent tickets
  • The top of the page shows totals for all tickets, Done, Overdue and Stalled (in Doing for more than five days)
  • Progress is counted on tickets that have no children

While the board is filtered to a single milestone, tickets created with a column’s + get that milestone too.