Record the schedule workflow that freezes after filtering
The issue report says the screen feels slow. Developers reproduce it with different data and disagree about which interaction is responsible.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Browser profiling · Reproducibility
Estimated field mix
- Performance engineering50%
- Quality engineering30%
- Frontend20%
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
A fictional repair coordinator opens a week containing 2,000 jobs. The initial page loads, but filtering and selecting a job can freeze the interface. Build a synthetic scheduling screen with keyboard operation before measuring changes.
Setup prerequisites
- Create a local schedule UI with 2,000 synthetic jobs, long labels, empty results and deterministic responses.
- Record browser version, viewport, device emulation, CPU/network throttling and build mode for every comparison.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Define a deterministic sequence: load 2,000 jobs, filter by technician, select the final visible job and clear the filter.
- Record build mode, browser version, viewport and any throttling alongside trace timestamps.
- Assert the selected job and final result count so an incomplete interaction cannot appear fast.
Implementation constraints
- Use only synthetic names and job descriptions; record navigation and interaction phases separately.
Verification to include
- Replay the sequence twice and confirm identical selected IDs and result counts.
- Run with an empty technician result and verify the sequence reports that expected state rather than timing an absent control.
Deliverables
- Browser workflow fixture and annotated baseline trace
Rollout and recovery
Keep the baseline workflow versioned before changing the page; fixture changes invalidate direct timing comparisons.
Value of the work
For the engineer: Connect bundle, rendering and interaction measurements to user-visible behavior without losing accessibility.
For the team: Produce a bounded performance investigation and regression workflow for dense operational interfaces.
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.