Keep report filter errors near their controls
Invalid date ranges produce a toast that disappears before users reach the fields. Add persistent linked errors.
- Focused work estimate
- 1h 45m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Forms · Error recovery
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
Fictional cooperative Quarry reviews synthetic service-volume reports. Build local report fixtures with empty, missing and delayed values.
Setup prerequisites
- Create synthetic report series with explicit missing values.
- Stub report loading, sorting and export responses.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Error names affected range
- Correction clears the message
- Submitted values remain editable
Implementation constraints
- Do not automatically reset user dates.
Verification to include
- Submit reversed range
- Correct only end date
Deliverables
- Date-filter errors and focus checks
Rollout and recovery
Fall back to explicit apply with inline errors.
Value of the work
For the engineer: Practice semantic data presentation and robust interaction.
For the team: Inspect whether reporting decisions remain possible without color or pointer use.
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.