Skip to main content

Kanban board

Route: /org/tasks?view=kanban · Permission: View Tasks To move a task: Change Status of Task

1. What the Kanban view is​

One column per status, in the order you configured them, with every task as a card. Dragging a card between columns is a status transition — the same operation as changing the status in the detail panel.

KanbanListTable
Columns areStatuses—Fields
Grouping producesSwimlanesHeadingsGroup rows
Primary actionChange statusRead and expandEdit fields
Shows hierarchyFlattened, with a breadcrumbNestedNested
Respects the workflowYes — visiblyn/an/a

2. How the board relates to configuration​

3. Using the board — step by step​

Figure 1 — The board with columns, counts and cards.

Step 1 · Read a column​

#ElementNotes
1Colour dotThe status colour
2Status nameUppercase
3Count pillNumber of cards in the column
4CollapseNarrows the column to a vertical label with its count

An empty column shows a dashed drop zone reading Drop items here.

Columns render a limited number of cards and offer Load More (n) at the foot when there are more.

Step 2 · Read a card​

Figure 2 — One card with pips: 1 breadcrumb, 2 key, 3 priority flag, 4 type icon, 5 Billable pill, 6 hours + progress %, 7 Log Time, 8 Add Comment, 9 due date, 10 assignee avatar.

Everything on the card comes from the task's own configuration: the flag takes the priority colour, the icon is the task type's, and the percentage is actual hours against the estimate.

The breadcrumb above the title only appears on a subtask — on this board it is the only sign that a card has a parent.

#On the cardMeaning
1BreadcrumbThe parent chain, shown only on subtasks — Parent > Child
2Task keyMonospace reference
3⚑ PriorityFlag glyph in the priority colour, with its name
4Type iconThe type's icon, tooltipped with its name
5BILLABLE pillPresent when the task is billable
6Hours and %Actual against estimate, as a percentage capped at 100
7Log TimeOpens the log-time modal without leaving the board
8Add CommentOpens the comment modal
9Due dateFormatted MMM d
10Assignee avatarA ? when unassigned
The breadcrumb is how you tell a subtask apart on this board

Kanban flattens the hierarchy — subtasks are cards in their own right, sitting in whatever column their own status puts them. The breadcrumb above the title is the only indication that a card has a parent.

Step 3 · Move a card​

Drag it. The target column shows a dashed overlay reading Drop Here — "to move to <status>".

Only columns the workflow permits will accept the card

The board reads the project's workflow and computes the legal destinations from the card's current status. A column that is not a permitted target does not accept the drop, and the move is refused silently — no toast, no error.

If a drop appears to do nothing, that is why. Check the workflow graph.

With no workflow saved, every column accepts every card

The board falls back to allowing a move to any status when the project has no transitions defined. So a project that has never had its workflow drawn is more permissive than one that has.

Step 4 · Group into swimlanes​

Setting Group by turns the board into horizontal swimlanes, each with a full set of status columns:

Group bySwimlane perTrailing lane
CategoryTask categoryUncategorized, only if any exist
TagTagUntagged
Project Phase / MilestoneMilestoneUnaligned / Backlog

Each swimlane header carries the group's icon, name and a count.

4. Field reference — what the board does and does not do​

ControlBehaviour
Drag a cardTransits the task. Blocked by the workflow and by Change Status of Task
Click a cardOpens the detail panel
Log TimeModal; logs against that task
Add CommentModal; posts a comment
Collapse a columnVisual only, not persisted
Load MoreReveals more cards in that column

Which statuses appear as columns​

Columns come from the project's status configuration, sorted by order. With Hide Done on, any status whose category is Done is removed — and, for statuses with no category recorded, the ids done and cancelled are removed as a fallback.

Hide Done means something different here than in List and Table

Kanban decides by status category; List and Table decide by hard-coded status id. A custom Closed status in the Done category disappears from the board and stays in the list.

What a drop actually sends​

A drop calls the task transition endpoint with the new status id, then refetches the board. It does not go through the generic task update — so the workflow's transition actions and conditions apply to it exactly as they would to a status change made anywhere else.

5. The admin contract​

PrerequisiteWithout it
At least one statusNo columns
A saved workflowEvery column accepts every card
Change Status of TaskCards can be dragged but the move is rejected
Status order set sensiblyColumns appear in a confusing sequence
Status categories set correctlyHide Done misbehaves, and completion metrics are wrong

6. Downstream​

ActionEffect
Drop a cardStatus changes; workflow actions fire; the activity log records it
Log Time from a cardA time log against the task, visible in Time logs and timesheets
Add Comment from a cardA comment, with the usual notifications

7. Don't confuse this with…​

ThingWhereWhy it is different
Kanban (this page)?view=kanbanColumns are statuses
List groupingListGroups are headings, not columns
SwimlanesHere, with Group byRows of columns, not a different view
Resolution Queue/org/resolve/queueTickets, not tasks
TimelinesGanttTime, not status

8. Troubleshooting​

SymptomCause
A drop does nothingThe workflow does not permit it — silently refused
A drop is refused for one user onlyThey lack Change Status of Task
A status has no columnHide Done removed it, or it is not in the status config
Columns in the wrong orderSet order on the Statuses tab
A card shows a breadcrumbIt is a subtask
Not all cards are visibleColumns cap what they render — use Load More
Hide Done differs from the listThe two views decide "done" differently
Every column accepts every cardNo workflow has been saved