Boards and workflow

Boards and backlog setup

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 BoardColumns line items add BoardColumnStatuses line items linking each column to one or more WorkflowStatuses and set WipLimit per column. Project Lead opens the Backlogs row for the Project and sets the GroomingCadence (Weekly / BiWeekly / Monthly / AdHoc).

Daily execution

Developers move their assigned Issues along the Workflow — ToDo → InProgress (stamps Issues.StartedAt, emails Assignee, places card in In Progress column on the Board), work the Issue (commit time via IssueWorkLog, post IssueComments, attach files via IssueAttachments, decrement Remaining), open a git PR that the auto-link-to-pr webhook captures into PullRequestLinks (PR opening records linkage only; Projects.AutoTransitionOnMerge applies only to a verified merge). Every status change runs through status-transition-routing, which validates the move against the matching WorkflowTransitions row, blocks if RequiredApproverRole 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 BoardColumns.WipLimit is exceeded. Every change appends an IssueHistory audit row.

Standup, blockers, and bug triage

The daily-standup-digest schedule fires weekday mornings at the Project’s StandupTimezone, 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 NotifyTo channel. Issues Status: Blocked carry an IssueLinks row of type IsBlockedBy pointing at the blocker; resolving the blocker (transitioning the blocking Issue to Done) runs the UnblockLinks on-transition action. Bugs created or updated trigger bug-priority-recompute to refresh PriorityScore from Severity + ReportedFrequency + ReachEstimate; threshold crossings flip Priority: Critical and notify the on-call Engineer + Project Lead.

Handle the last available review slot

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 WipLimits 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.