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.
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 columns | The columns of the board and the status a task takes on when dragged into one. Dragging is therefore the same as setting a status. |
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. |
Default isDefault | no | yes/no | Which board appears when the project is opened. |
Settings & permissions
- Module
module.projects. projects.project.viewfor the project,projects.task.manageto change work items.- 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.
Tasks and tickets have different columns. Correct. Both carry their own status catalogue; the board notes that on the respective lane.
A person is missing from the person view. Lanes are shown for owners with work items. Somebody with nothing assigned gets no lane.