Point requesters to the field that needs fixing
An incomplete request produces only Invalid request. Add field feedback and an error summary for vendor, business reason, and delivery date.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Form validation · Accessibility · API errors
Estimated field mix
- Frontend50%
- Accessibility50%
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 Beacon operations team buys equipment through a browser form. Finance checks totals, departments, and quotes. Scope is one currency per request and an approval API contract; payments and accounting integration are excluded.
Setup prerequisites
- Synthetic department and cost-center directory
- Draft, submission, and approval API fixtures
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Invalid submission focuses a summary with links to fields.
- Each error is associated with its field and stays visible until resolved.
- Entered values survive client and server validation failures.
Implementation constraints
- Map known server field errors and use a safe general fallback for unknown errors.
Verification to include
- Submit an empty form by keyboard and follow each summary link.
- Return an unknown server validation code; preserve values and display an actionable general error.
Deliverables
- Accessible validation summary and server-error mapping cases
Rollout and recovery
Ship behind the form flag; restore the earlier route if requesters cannot correct errors.
Value of the work
For the engineer: Practice form modeling, exact totals, revision handling, and collaboration under failure.
For the team: Inspect whether a developer protects business workflows from duplicate, lost, or misleading submissions.
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.