Admin Intake List Editing
Summary
Section titled “Summary”The Admin Intake List Editing mockup documents the React intake queue editing work for JMS-5418 and JMS-5419. It keeps the staging-parity intake list, case drawer, filters, sorting, pagination, saved views, inline Status and Assigned To editing, Gmail-style selection, staged bulk changes, Archive confirmation, and partial-result recovery in one admin workflow.
Mockup Snapshot
Section titled “Mockup Snapshot”| Field | Value |
|---|---|
| Company | JMS |
| Portal | Admin |
| Prototype | https://jms.orchidux.com/admin/intake |
| Jira tickets | JMS-5418, JMS-5419 |
| PRD | Not linked yet |
| Handoff status | In review |
| Walkthrough video | Not attached yet |
What Is Stable
Section titled “What Is Stable”The approved baseline commit is 5da70c4ba76a830603609dafac8428422e4ec1e7, approved on 2026-08-12. Stable shared behavior is also reflected in PRODUCT.md and FEATURES.md, including URL-backed filters, responsive cards, row selection, staged bulk save, inline editing, saved views, Archive as a confirmed bulk action, and row-level success/failure review.
In-Review Scope
Section titled “In-Review Scope”The current handoff remains in-review. Treat the latest matching-type scoped Status editor behavior and related refinements as review material until product approval closes.
Product Notes
Section titled “Product Notes”- Intake defaults to IP cases and ID-descending order.
- Search, filters, sorting, pagination, and saved-view state are represented in the URL.
- Inline Status and Assigned To editors apply to one case and expose only valid values for that case.
- Bulk Status and Assigned To changes are staged together and saved with one action.
- Archive is bulk-only and requires an explicit reason before applying.
- Bulk result details must account for every changed and failed case.
Open Follow-Up
Section titled “Open Follow-Up”Finalize the UX Registry row after deployment with the shipped route, source bundle, thumbnail state, and documentation URL for this page.