Kanban board

On the board you see not only what exists but where it stands — and you move it with a gesture instead of a form.

Today the board is available for projects. You reach it via the view switcher in the top right, next to list and explorer.

The columns

Each column is one status value of your projects — in the order your organisation defined on the entity type. Out of the box these are Planned, In progress, Completed and Stopped.

Three things you will notice:

Empty columns stay. That nobody has completed anything right now is a statement — it would be lost if the column simply disappeared.
“Unspecified” collects everything that has no status yet. This column only appears when such projects exist.
If a project carries a status value the schema does not (or no longer) know — from an old import, say — it gets its own column at the end. Nothing disappears.

The number next to the heading counts all projects in that column, not just the first page that was loaded.

Moving a project

Drag the card into another column — that’s it. What happens is exactly what happens via Edit → change status → Save & publish:

If your tenant runs in approval mode liberal (the default), the change takes effect immediately.
Under consensus, consent or highlander a draft is created that waits for approval. You get the notice “Draft submitted — awaiting approval”, and the card visibly returns to its place. It never claims a change that has not happened. You find the draft under Drafts.

When a card cannot be dragged — and why it shows that beforehand instead of failing on drop:

Reason	What to do instead
You lack write or draft permission on projects	Your administration handles permissions
Project data is managed by a connector	The status is maintained in the source system (banner above the list)
You are working inside a scenario	Scenarios do not publish — leave the scenario first

Clicking a card opens the detail page, as everywhere.

The lanes (swimlanes)

Above the board you can switch lanes on. The board then splits into horizontal bands:

by role — one band per role staffed on projects.
by person — one band per human being.

The person lane is the interesting one: in roleALPHA projects are not attached to people directly. They are attached to the role staffed on them (“staffs”, technically ASSIGNED_TO) — and that connection carries the concrete people who fill the role on this project. Those are what the person lane shows. It is therefore more precise than “everyone who holds that role somewhere”: whoever holds the role but does not work on this project does not appear here.

How to create that connection is described in Participants on a relationship.

A project appears in several lanes — on purpose

If two roles work on a project, it appears in both bands. The lanes show involvement, not ownership. The status belongs to the project, not to the lane: drag one of the cards and its siblings move along.

When a lane stays empty

The band “Unassigned” at the end collects everything without a staffing. A project without staffing is not an error — it is an open position.
If an axis is not offered at all, the corresponding relationship type is missing in your tenant. It would only show empty bands, and that would look like “nobody is assigned”. Your administration can add the type.

What your organisation can configure

The board is not hard-wired: which field spans the columns and which relationships carry the lanes is declared in the entity type’s JSON schema under x-kanban — in the same place as the card declaration. If you run several project types, each gets its own board.

Details in Entity type schema.