Enforce same-organization case-to-project references with a foreign key
An import can connect a case in one organization to a globally valid project in another organization.
- Focused work estimate
- 3h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Foreign keys · Tenant isolation
Estimated field mix
- Database engineering60%
- Security40%
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
A fictional case-management application filters most requests correctly, but imports and background commands can connect a case to another organization's project or assignee.
Setup prerequisites
- Create two synthetic organizations with overlapping display names.
- Use repository-level authorization and migration-backed constraints.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Create a composite foreign key including organization identity.
- Reject mismatched direct SQL and application writes.
- Retain valid same-organization associations.
Implementation constraints
- Backfill and inspect existing mismatches before validating the constraint.
Verification to include
- Insert a valid synthetic case/project relationship.
- Insert a cross-organization relationship directly and observe database rejection.
Deliverables
- Tenant-bound foreign-key migration
Rollout and recovery
Validate after a clean discrepancy report; quarantine invalid legacy relationships without guessing ownership.
Value of the work
For the engineer: Practice tenant-aware keys, foreign keys and direct-write denial tests.
For the team: Review defense in depth for data isolation across ordinary and privileged writers.
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.