Link procurement error summaries to affected fields
Required fields missing gives no location. Add field errors and a navigable summary.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Accessibility · Validation
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 procurement team Northroom collects purchase requests in a browser form. Work uses local stubs and cannot place purchases.
Setup prerequisites
- Create synthetic categories and conditional request fields.
- Stub draft revisions and submission outcomes.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Summary links focus fields
- Labels expose required state
- Corrections clear only relevant errors
Implementation constraints
- Use stable description IDs.
Verification to include
- Follow summary link
- Submit several missing values
Deliverables
- Summary and keyboard checks
Rollout and recovery
Retain field errors if summary navigation fails.
Value of the work
For the engineer: Practice state boundaries and form schema transitions.
For the team: Inspect how hidden obsolete data and duplicate requests are prevented.
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.