Work to verified outcome

Step by step

1. Work the board Developer / Engineer

   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.

   • Validate transitions and atomic WIP limits
   • Updates Issues, Workflow transitions, Board columns

2. Resolve blockers Developer / Engineer

   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.

   • Preserve other outstanding dependencies
   • Updates Issue links, Issues

3. Verify result QA / Tester

   When a git PR linked to an Issue is merged into the protected branch, the auto-link-to-pr webhook updates the pull request links row (Status: Open → Merged, merged at stamped); if project auto transition on merge is on, the Issue auto-transitions in review → Done (subject to any QA gate in workflow transitions). On in review → Done, status-transition-routing flips issue resolved at, issue resolution: Fixed, recomputes current sprint progress without incrementing an unversioned historical counter, and unblocks any issue links of type is blocked by pointing at this Issue. QA verification of bug-type Issues holds at in review until QA approves the gated transition.

   • Record independent quality evidence
   • Updates Transition approvals, Pull request links, Issues
   ApprovalA person approves before the work moves on.

Developer / Engineer

Delivery contributor. Works assigned Issues, transitions Status, logs work, comments, attaches files, opens PRs that auto-link back.

QA / Tester

Quality role. Files and verifies bug Issues, transitions Issues through the verification gate, signs off on in review → Done for Bug-type Issues.

Scrum Master / Iteration Manager

Runs the Sprint cadence and the Board. Owns ceremonies (planning, standup, review, retro), WIP discipline, and the burndown.