Bugs and verification

Issue intake

Issues land in the system through three paths: (a) UI creation by Developers, QA, or the Project Lead; (b) Reporter creation by internal users outside the squad (constrained to Bug / Task / Improvement / Incident types); © the issue-creation-from-webhook workflow firing on inbound email, Slack /issue slash command, support-helpdesk Ticket promote, or it-itsm Incident promote. The webhook code resolves target Project + Component from routing rules (subject prefix, channel, sender domain), creates the Issues row with Status: the Workflow’s InitialStatus, Priority: Medium defaulted, and emails the Reporter with the IssueKey acknowledgement. Bug-type Issues trigger bug-priority-recompute immediately.

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.

PR-merged Done flow

When a git PR linked to an Issue is merged into the protected branch, the auto-link-to-pr webhook updates the PullRequestLinks row (Status: Open → Merged, MergedAt stamped); if Projects.AutoTransitionOnMerge is on, the Issue auto-transitions InReview → Done (subject to any QA gate in WorkflowTransitions). On InReview → Done, status-transition-routing flips Issues.ResolvedAt, Issues.Resolution: Fixed, recomputes current sprint progress without incrementing an unversioned historical counter, and unblocks any IssueLinks of type IsBlockedBy pointing at this Issue. QA verification of bug-type Issues holds at InReview until QA approves the gated transition.

Keep a merged fix waiting for required verification

A pull request can be merged while its bug still needs verification. The authenticated merge event updates the link and its observed branch/check context. It cannot supply the QA decision required by the issue’s current workflow. Keep the issue at the review gate until a qualified independent tester approves the exact submitted revision.

A changed issue or revised fix invalidates an earlier decision where its evidence no longer applies. The tester records what was reviewed, who requested the decision and the result. A person who prepared the protected work cannot approve their own gate merely because they also hold a QA role.

A resolved blocker removes only that dependency. Other blockers, missing required estimates or unresolved review gates still apply. Preserve the distinction between a duplicate report, a declined change and a verified fix so reports do not count every terminal status as completed delivery.