Overview#
Investigators do not live in empty home screens. They live in queues: overnight intakes, supervisory assignments, partner referrals, and cases waiting on the next analytical step. Opening the wrong case wastes the first coffee of the shift. Losing queue context because a create-related-investigation call failed is worse. Teams evaluating Argus against legacy RMS products judge the queue experience quickly, because it is where volume work either feels calm or feels like a fight with the UI.
The Investigation Case Queue gives investigators and supervisors a managed list, a selection model that does not yank them away on every click, and an inspector summary strong enough to decide whether to open the full workspace. Opening an investigation starts from the selected queue item. When creating related work fails, the error stays inline and the queue remains usable. The feature sits alongside collaboration and case management services already on the platform, rather than inventing a second case store.
Last Reviewed: 2026-09-15 Last Updated: 2026-09-15
Key Features#
-
Managed queue browsing: Lists cases waiting for attention under the operator's grants, including supervisory views over team workload where authorised.
-
Selection without forced navigation: Operators can move selection through the list while the inspector updates, supporting triage rhythms used in real watch floors.
-
Inspector summary: Enough metadata to decide open versus defer, without loading the full graph and evidence workspace on every hover through the queue.
-
Open from queue context: Starting an investigation carries the selected item's identity so analysts do not re-search for what they were just looking at.
-
Creation failure resilience: Related-create failures display clearly and preserve queue state, which matters when validation or authorisation rejects a new investigation mid-triage.
-
Shared denied and failed states: Aligns with the wider fe2 audit language for empty, denied, and failed panels.
-
Collaboration adjacency: Works with case collaboration and assignment tooling so queue items reflect real ownership rather than anonymous piles.
Use Cases#
-
Morning triage: A supervisor walks the queue, inspects each item, and opens the highest priority cases for assignment.
-
Shift handover: Outgoing and incoming analysts share the same queue selection and inspector context during verbal handover.
-
Partner referral intake: Referrals land in the queue; investigators inspect before committing a full workspace session.
-
Failed create recovery: An investigator corrects validation errors on a related investigation create and retries without losing their place.
Integration#
Case and investigation services provide queue contents and inspector payloads. fe2 investigation UI hosts the list and inspector. auth_service grants decide which queue slices are visible. Collaboration services contribute ownership and assignment signals. Graph and evidence modules remain one open action away once the investigator commits.
Open Standards#
- NIEM-oriented case exchange practices: Case identifiers and status values remain compatible with broader case-exchange conventions used across Argus investigation modules.
- WCAG 2.2: Queue selection and inspector controls remain keyboard reachable with visible focus.
- ISO 8601: Queue timestamps and ageing displays use unambiguous time formats.