Boards and workflow

Scrum Master creates the Boards for the Project — a Scrum board for the squad, an optional triage board for inbound bugs, an optional release board for the active Version. Each Board’s board columns line items add board column statuses line items linking each column to one or more workflow statuses and set wip limit per column. Project Lead opens the Backlogs row for the Project and sets the grooming cadence (Weekly / bi weekly / Monthly / ad hoc).

Developers move their assigned Issues along the Workflow — to do → in progress (stamps issue started at, emails Assignee, places card in In Progress column on the Board), work the Issue (commit time via issue work log, post issue comments, attach files via issue attachments, decrement Remaining), open a git PR that the auto-link-to-pr webhook captures into pull request links (PR opening records linkage only; project auto transition on merge applies only to a verified merge). Every status change runs through status-transition-routing, which validates the move against the matching workflow transitions row, blocks if required approver role is unmet, and runs the per-transition action. Every move into a column also runs wip-limit-enforcement, which blocks if the destination column’s board column wip limit is exceeded. Every change appends an issue history audit row.

The daily-standup-digest schedule fires weekday mornings at the Project’s standup timezone, posts the per-squad digest (In-Progress moved-yesterday, Done moved-yesterday, Blocked, At-Risk by sprint days remaining vs. remaining estimate) to the Project’s notify to channel. Issues Status: Blocked carry an issue links row of type is blocked by pointing at the blocker; resolving the blocker (transitioning the blocking Issue to Done) runs the unblock links on-transition action. Bugs created or updated trigger bug-priority-recompute to refresh priority score from Severity + reported frequency + reach estimate; threshold crossings flip Priority: Critical and notify the on-call Engineer + Project Lead.

Two developers may try to move work into a review column that has room for one more issue. The transition service checks the effective limit and reserves the destination under the same operation. Both requests cannot claim the last slot based on an earlier screen count.

A dated wip limits override takes precedence over the column’s default. Zero blocks new entry; an absent limit means unlimited. Lowering a limit below current occupancy keeps existing work visible and blocks additional entries until the team resolves the excess. It does not delete cards or invent an exception.

An issue may appear on more than one configured board. Apply every affected limit using validated board membership and current workflow state. A personal filter cannot hide work from the server’s WIP count. Dragging a card, applying a bulk edit and receiving a provider event all use the same transition checks and preserve the same history.

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