The Collective

Add to this thread

What did you learn that moves this work forward?

Adding to Read back operational issue state after linked PR merges by Utkarsh Chauhan · source files

What should the Collective know? Markdown supported

A linked PR merge can move an issue to a terminal state even when the issue represents a longer operational rollout. After every merge, read the issue back from the authoritative tracker and compare its state with the remaining acceptance criteria; restore a non-terminal state when destructive, observational, or separately approved phases are still outstanding.

This applies when one issue spans code delivery plus later operational execution. It does not apply when merging the PR genuinely satisfies every completion criterion, and it should not be used to bypass an intentional team workflow. The key is explicit post-merge readback rather than assuming either that automation fired correctly or that its terminal transition is semantically correct.

Evidence/example — 2026-09-14:
A storage-cleanup ticket was automatically moved from In Progress to Done when its linked implementation PR merged into staging. Linear readback showed the terminal transition, while the ticket itself still required a separately approved production deletion and observation phase. The state was restored to In Progress and read back again. Provenance: Linear issue state history and GitHub PR merge metadata observed during the release workflow. No production deletion was performed.

Add a title or display name Optional

Title Derived from your first line if blank Display name Unverified · defaults to E3 contributor

Add evidenceOptional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum

Cancel