A resolved unowned case sits in Unassigned — triage forever: the tab filters is_closed, which only flips on closed #1145

Found while building the claim-seam fixtures for #1096 (PR #1143). Not fixed there — it is a view/lifecycle question, not the claim seam, and the claim seam's file surface was exclusive.

The mismatch

unassigned_triage (src/views/case.view.ts) filters:

filter: [
  { field: 'owner_id', operator: 'is_null' },
  { field: 'is_closed', operator: 'equals', value: false },
],

and is_closed is derived by case_sla_defaults as effStatus === 'closed' — resolved does not set it. That is deliberate elsewhere and correct there: _case-assignment.ts records the same distinction for load balancing, where CLOSED_CASE_STATUSES is ['resolved', 'closed'] precisely because is_closed is the wrong predicate for "no longer live work", and case_sla_monitor settled it the same way with $nin.

So a case that is resolved and still ownerless satisfies both filters and stays in the triage tab indefinitely. The tab's own empty-state copy says the rows are cases that "arrive with no owner", and its purpose is "work waiting for a human" — a resolved case is neither.

Reachability

Real but narrow, and it widens slightly with PR #1143:

• an agent can resolve an unowned case straight out of triage (the feat(sharing): let service agents see the unowned cases they triage (#1096) #1134 share grants edit) without claiming it — feat(service): let an agent claim an unowned case out of triage (#1096) #1143 deliberately excludes resolved from the claim gesture, on the grounds that finishing a case is not picking it up, so this path leaves a resolved ownerless row behind by design;
• a seeded/imported case can arrive resolved and ownerless.

Both leave a row that reads as backlog and is not.

Same predicate, three spellings

Worth settling once rather than per-consumer — the app currently expresses "no longer live work" three ways:

The sharing rule matters most: it grants an agent edit on every resolved ownerless case for the same reason the view shows them.

Options

• A. Change the view (and the sharing rule) to status $nin ['resolved','closed'], matching the hooks. Narrowest, and makes the four spellings agree.
• B. Make is_closed mean "not live" (set it on resolved too). Wider blast radius — is_closed is a stored, indexed column that reports and other views read, and the name would then disagree with the closed status.
• C. Leave it and treat a resolved ownerless case as genuinely needing triage attention (someone should own what was resolved).

No recommendation attached deliberately — the choice between A and C is a product judgement about what the tab is for, and B changes a column's meaning app-wide.

Filed unassigned, per Prime Directive #10.