Clear an orphaned cost center when department changes
Selecting Marketing / Events and then changing to Engineering leaves Events hidden in the payload. The reviewer has to send the request back.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Dependent forms · Async state · Data integrity
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
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
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Department changes clear any incompatible cost center.
- Loading and unavailable directory states differ from an empty directory.
- A previous department response cannot replace active options.
Implementation constraints
- Store stable directory IDs and explain why a selection was cleared.
Verification to include
- Switch Marketing / Events to Engineering; the field and payload both lose Events.
- Reverse response order and reject the active request; stale options remain unavailable.
Deliverables
- Dependent-select fix and delayed-directory tests
Rollout and recovery
Release after synthetic department-switch checks; prevent submission if required directory data is unavailable.
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.