Migrate one procurement draft schema transition
A category field changes shape while drafts remain open. Add one deterministic version migration.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Schema evolution · Compatibility
Estimated field mix
- Frontend100%
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
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- CFORM-101 · Preserve procurement amount precision during editing
- CFORM-103 · Remove obsolete shipping fields on procurement category changes
- CFORM-102 · Link procurement error summaries to affected fields
- CFORM-104 · Allow earlier procurement corrections after final-step errors
- CFORM-105 · Show acknowledged and unsaved procurement draft states
Acceptance criteria
- Old version migrates predictably
- Future versions stay read-only
- Dropped fields appear in review
Implementation constraints
- Preserve original draft until acknowledgement.
Verification to include
- Migrate old fixture
- Open unsupported future version
Deliverables
- Migration and preserved-original cases
Rollout and recovery
Restore old reader using preserved drafts.
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.