Completed work to release cut

Step by step

1. Reconcile code evidence Developer / Engineer

   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.

   • Verify branch, checks and source event identity
   • Updates Pull request links, Integration events

2. Review release scope Project Lead / Product Owner

   As Issues complete with fix version = <version>, the Project Lead readies the Version. On version status: Unreleased → Released (typically after a release-board sign-off and CI green), release-cut-from-version fires, validates every Issue in the proposed version is completed or explicitly excluded before the reviewed release scope is frozen; for those eligible Issues, stamps released at, applies an issue labels row released-<version>, updates parent epic progress rollups, and emails the release-notes digest (Issues grouped by Type — Story / Bug / Improvement) to the Stakeholder distribution list. A Released Version is not modified — additional fixes ship in the next Version.

   • Freeze eligible completed issue scope and source revision
   • Updates Versions, Issues
   ApprovalA person approves before the work moves on.

3. Share progress Project Lead / Product Owner

   Every role sees a scope-appropriate dashboard: Developer sees My Open Issues + the Active Sprint Board; Scrum Master sees Sprint Burndown + Velocity Trend + Stalled Issues + WIP Warnings; Project Lead sees Backlog Health + Release Progress + Epic Progress; QA sees Bugs Awaiting Verification + Bug SLA Attainment; Stakeholder sees Epic Roadmap + Release Forecast for assigned Projects; Reporter sees My Reported Issues; Admin sees Workflow + issue type health. The Sprint Velocity Report and Sprint Burndown drive the ceremonies; the Cycle Time / Lead Time and Throughput by Type reports drive process improvement; the Release Forecast and Epic Roadmap drive stakeholder communications.

   • Publish permitted dated delivery context
   • Updates Epic progress, Milestones

Developer / Engineer

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

Project Lead / Product Owner

Owns the Project end-to-end — backlog priority, release planning, estimate overrides, scope decisions. The DRI for the product the Project ships.

Stakeholder

Read-only audience for an assigned Project — executive sponsor, adjacent team lead, internal customer. Sees the board and the roadmap but cannot change anything.