Project boards
Overview
A board shows a project's work as a wall rather than a list — the view in which you see where something is stuck instead of working it out.
What sets it apart from ordinary boards: it shows tasks and tickets side by side. Both are work items of the same data model but carry separate status catalogues — a ticket passes through different states than a task. The board says so rather than forcing both into the same columns.
Core tasks
Narrow it down. The filter offers All, Tasks and Tickets; Hide completed clears the wall. The header names the current view and the number of tasks and tickets.
Group by person. By person switches the wall from status lanes to person lanes. Anything unassigned lands in the Unassigned lane — in practice the most important one, because work without a name attached stays put.
Create a task. New task captures directly on the board, without the detour through the list.
Spot blockers. If a work item is blocked by a dependency, the card says so instead of appearing workable.
Track time right on the card. Every card carries a stopwatch. One click starts it for exactly this work item — and the card moves into the follow-up status configured on its status (default: Open → In progress) without reloading the board. While it runs, the card shows Pause and Stop & book; pausing and stopping do not change the status. Which status leads where is set in the task settings; the time itself lands in time tracking.
Manage columns. Columns in the board header opens the column management: add a column (name and task status), rename it, drag to reorder, set an own limit or delete the column. The name is the label on the board — "In progress" may read "Running" here without renaming the status. Each status appears at most once per board. After closing, the board shows the new columns. Column management needs the permission to edit the project.
Refresh. The wall can be reloaded when several people are working at once.
Fields in detail
The What it does column answers what changes in the system — not what the field is called. The grey name behind the label is the API field: the same thing runs under that name through automation, import and AI tools.
Creating and editing a board
| Field | Required | Values / format | What it does |
|---|---|---|---|
Name name | yes | text, max. 255 characters | What the board is called in the project. Several boards per project are allowed — say one for delivery and one for acceptance. |
Project projectId | yes | an existing project | Which project the board belongs to. |
View viewType | no | kanban, list, gantt | How the same tasks are shown. The view changes nothing about the data; it changes what you notice — congestion on kanban, order in a list, dates on a gantt. |
Columns columns | no | list of task statuses | The board's status selection in column order; the status is what a task takes on when dragged in — dragging is therefore the same as setting a status. The selection creates or aligns the columns (new statuses become columns named after the status, deselected ones disappear); names and limits are maintained in the column management. If a column with its own name or a WIP limit would disappear, the dialog asks before saving — the name and limit are lost with the column. |
Limit per column wipLimit | no | number | How many tasks may sit in a column at once. Above the limit the board warns — the point is to make started work visible instead of piling it up. All open items of the project in that column count, including filtered ones; done and archived items do not. The board's detail view in the API reports the same state (wip: count, limit, reached, exceeded) — for automation and AI tools. The limit blocks nothing. |
Default isDefault | no | yes/no | Which board appears when the project is opened. |
Board columns
Via Columns on the board or the API /v1/project-boards/{ulid}/columns.
| Field | Required | Values / format | What it does |
|---|---|---|---|
Name name | yes | text, max. 255 characters | The label of the column on the board. |
Task status statusKey | yes | status from the task settings | Which items stand in the column — and which status a card gets when dragged in. At most once per board. |
Limit (WIP) wipLimit | no | number, empty or 0 = none | The work-in-progress limit of this column; it beats the board's limit. Counting and effect as there: the board warns from the limit on, it blocks nothing. |
Order sortOrder | no | number, ascending | Where the column stands. Drag to reorder in the management; a new column goes to the end. |
Settings & permissions
- Module
module.projects. projects.project.viewfor the project,projects.task.manageto change work items.projects.project.editfor column management — in the project's brand; whoever may only read the
project sees the columns but cannot change them.
- Task statuses come from the core (Task settings), ticket statuses
from the ticket module. The board renders both but defines neither.
- External contributors see only work items assigned to them, where the project is set that way.
FAQ & troubleshooting
Tickets do not appear. Either the project has none, or the ticket module is not active. The wall says so explicitly.
A card cannot be dragged to the next column. Check whether it is blocked by a dependency — and whether you hold the permission to change it.
A column cannot be added: "This status already has the column … on the board". Each status appears only once per board — otherwise the board would not know which column a card belongs to. Rename the existing column instead of adding a second one.
Tasks and tickets have different columns. Correct. Both carry their own status catalogue; the board notes that on the respective lane.
The card does not move to "In progress" when the stopwatch starts. Then its current status has no follow-up status configured, or the target status is deactivated — that is intended and maintained in the task settings.
A person is missing from the person view. Lanes are shown for owners with work items. Somebody with nothing assigned gets no lane.