Keep shared queue links useful after refresh
A shift lead shares the unassigned billing queue, but recipients land on All tickets. Put filters in the URL so opening the link, refreshing, and using Back retain the intended view.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- URL state · React · Navigation
Estimated field mix
- Frontend100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
The fictional Alder support team handles billing and delivery conversations in a browser console. Agents keep several tickets open, share filtered queues, and work through unreliable office Wi-Fi. The API contract returns ticket revisions and cursor-based pages; work stays within the console and its test adapter.
Setup prerequisites
- A ticket-list and reply API contract to implement or stub
- Synthetic conversations across two organizations with revision conflicts
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Status, team, and reference filters round-trip through the URL.
- Unknown filter values use documented defaults without crashing.
- Back restores the preceding filters and clears any cursor invalidated by them.
Implementation constraints
- Reference search targets synthetic ticket IDs; customer message text must not enter query parameters.
Verification to include
- Open team=billing and status=unassigned in a fresh tab and inspect the request.
- Use an unknown status, then navigate Back after two filter changes; verify fallback and history order.
Deliverables
- Queue URL parser and browser navigation regression case
Rollout and recovery
Enable URL filters for the internal queue; a flag restores the default queue without invalidating ticket links.
Value of the work
For the engineer: Practice state ownership, asynchronous races, accessible interaction, and recovery in bounded changes.
For the team: Inspect how an engineer protects agent work and handles failures that interrupt support operations.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.