Boards and workflow

Board Owner defines an active board, its timezone, ordered Columns, allowed source moves, optional Custom Swimlanes and Labels. Set each column’s wip limit and requires approval policy. Invite the intended internal roles through explicit board memberships. Proposed changes must preserve a valid column for every active task before a new workflow revision is accepted; archived columns with active work cannot simply be deleted.

Member requests a permitted move from the current column using the expected task revision. Resolve the active workflow revision, allowed source path, blockers and effective destination WIP limit. Reserve the destination and update current column plus derived Status atomically. Set started at on the first Doing entry of the current cycle, append task events and retain the order change. A drag, keyboard action or bulk request uses the same checks.

The move service consumes an Approved transition requests decision once, rechecking current revision, blockers, mandatory checklist policy and destination capacity. Mark Applied only when the move commits. Entering Done stamps completed at and appends one Completed task events row for Task plus cycle number. An approved request with no free slot remains approved but unapplied until it can be safely retried; approval alone is not completion.

Board Owner can reopen completed work through an allowed current workflow move with a recorded reason. Preserve the original completion event, increment cycle number and start a new work cycle without rewriting earlier timings. Recheck WIP and applicable approval policy for the destination. Archiving removes a task from active lists but preserves its relationships and event history; it cannot be used to remove evidence from an open review.

A team can have two review columns with different limits. Moving into either checks its current population, including cards hidden by personal filters. Zero blocks new entry; a blank limit leaves the column uncapped. Lowering the limit below existing occupancy keeps current cards visible while preventing additional entries.

Owner and priority swimlanes organise the same tasks. They do not create copies or change who can read a card. A custom lane belongs to one board, and a move cannot borrow another team’s lane identifier.

Before replacing a column, the owner plans a valid destination for its current tasks and records the new workflow revision. A renamed column retains its historical identity. Archive unused structure deliberately so old events and approvals still explain the path a task followed. A Done card needs the controlled reopen action before it can enter a new cycle.

• Active Board. Open the current records for this module within your assigned role and permitted scope.