Boards, table, and map

Every project has three views of the same tasks. The toggle lives on the project, next to the work. Your last view is remembered for you; it does not change the project for everyone else.

Board and table show top-level tasks; subtasks stay in the task drawer. The map can unfold subtasks under a parent.

Board (Kanban)

Columns come from a board layout, not one-for-one from every status.

Drag a card to change its status. The other cards slide into place when you drop.
Dropping onto a completed column can spawn the next recurring task.
Cards show assignees, label, deadline risk, subtask progress, comment count, recurrence, and the task number.
A task that appears while you are looking at the board flashes honey and fades, so a teammate’s new card is hard to miss.

Collapse a column by clicking its title. The rail shows a dot per task (outline for unstarted, honey outline for started, fill for completed), then a +N if there are many. When columns no longer fit, the board scrolls sideways. Tall columns grow the board with them — the project pane scrolls, not each column.

Completed-category columns are always last, even if a saved layout omitted them.

Layouts (managers)

A project can store up to 12 layouts (for example “Delivery” vs “Internal”). Each layout is a named, ordered list of columns.

There is always a Default layout, derived from the project’s status catalog. You can override Default by saving a layout with that role.

Open the ⋯ menu on the board to switch layouts and, if you manage the project, to open Board setup. Drag columns there to change their order; completed columns stay last. Layout names appear in that menu only when the project has a layout besides Default.

Columns must match statuses the project actually has. Invalid columns are dropped quietly rather than breaking the board. Canceled statuses are not useful as columns.

Table

A dense list for selection and batch work. Column headers stay put; only the rows scroll (same pattern as Schedule and My Work). Rows start sorted by status (the project’s catalog order); click a column header to change.

This is the view for “select twelve cards and push the due date a week.” How selection and the floating batch bar work is on Tasks.

Filters attach to the list header and apply as you change them. Past a handful of filters they collapse behind one control; applied values stay visible as chips. Due by shows tasks due on that day or earlier (including overdue). Late shows only open overdue work. Named chips next to the view toggle remember a filter set — click one to apply it, click it again to clear. The × on a chip deletes that saved set.

Status groups

While the list is sorted by status it splits into groups, one per status, each with a count.

Tick a group’s checkbox to select every visible row in that status, or to clear just that group. While groups are on there is no select-all for the whole list (⌘/Ctrl+A still selects every visible row).
Click a group heading to collapse it. Collapsed work is out of the way and out of reach: its checkbox disappears, and Shift-range cannot reach it, so a batch edit can never touch a row you cannot see.
Drag a row into another group to change its status. Grab the row anywhere outside its own controls; the grip between the checkbox and the title is the hint. The honey line shows where it will land.
Drag a whole selection the same way: tick several rows, then drag any one of them. Rows you may not edit are left behind. Dropping into a different status clears the selection; rearranging inside one group does not.
Inside a group rows keep the order you arranged, the same order as the board — so dragging up and down inside a group is a real reordering, not just a status change.
Landing in a completed status can spawn the next recurring task, exactly as on the board.

The ⋯ menu next to the view toggle turns grouping off, or collapses and expands every group at once. Sorting the list by another column also turns grouping off (the menu unchecks). Turn it back on from the menu to snap the sort to status. That choice lives on this browser, not on your account.

Statuses with nothing in them still show a heading so you can drag work into them. Archived projects are read-only, so rows there cannot be dragged.

Map

The mind map is the signature view: workstreams as a compact rail on the left, tasks unpacking from the one you open. Tasks with no workstream sit under Unscoped.

Use it to see structure and what blocks what — not to process a Monday-style queue. Workstreams start closed; click one to open it (the previous one closes). Ready work has a honey ring; blocked work waits on an open predecessor. Click a task to light its chain. Create and edit still happen in the drawer; double-click empty space to start a task under the nearest workstream, or drop a task onto a hub to move it. Subtasks stay folded until you expand the parent. Done work stays on the board — the map is remaining work.

Preferences that are yours

Remembered per user, not for the hive:

Last view (board / table / map)
Collapsed columns
Similar chrome on the project

Board layouts (the column sets) are on the project and shared.

List grouping and collapsed groups are remembered on this browser rather than on your account — the way you read a list at your desk is not the same as on a shared machine.

Tasks · Projects · Features and decisions · My Work and Schedule