Make ticket switching predictable from the keyboard
An agent navigating by keyboard loses their place after closing ticket details. Define focus behavior for opening, closing, and removing the selected row.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Keyboard access · Focus management · React
Estimated field mix
- Accessibility60%
- Frontend40%
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
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Opening details moves focus to the detail heading or first intentional control.
- Closing returns focus to the originating row or a documented adjacent fallback.
- Shortcuts do not fire in text inputs or during input method composition.
Implementation constraints
- Shortcuts supplement semantic controls and the ordinary tab sequence.
Verification to include
- Open and close details using only the keyboard and inspect focus.
- Remove the originating row while details are open, then close; focus remains visible and useful.
Deliverables
- Focus restoration and keyboard walkthrough notes
Rollout and recovery
Ship focus restoration before shortcuts; disable shortcuts separately if they conflict with editing.
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.