Skip to main content

0002 — Separate the migration backfill into its own Story and Task

Delivery / Program Management — decision record (ADR-style).

Context​

The RFC's Detail 4.D chunk 11 (migration backfill job, CHG-004) was ticketed on 2026-07-21 as TF-3548, parented directly to Epic TF-3185 with no owning Story — a deliberate choice at the time, since chunk 11 isn't one of the RFC's traced 17 user stories (TEAM-S01…TEAM-S17, Detail 1.C); see rfcs/rfc-team-owner-field-and-team-permission.task-breakdown.md.

A 2026-07-22 jira-alignment-check pass flagged this as worth a deliberate call rather than an implicit exception: leaving a Task both story-less and carrying a stale [TEAM-S01] title prefix (cosmetic drift from an earlier draft) risked a future audit either wrongly linking it to TEAM-S01 or repeatedly re-flagging it as broken.

Decision​

Give the migration backfill its own Story-level tracking, the same pattern already used for the RFC's other post-RFC scope additions (TEAM-S18, TEAM-S19-NEG):

  • TF-3548 closed Won't Fix (2026-07-22) — no functional change to the backfill job itself; closed purely to retire the story-less/mistitled ticket. Comment on the ticket records the supersession and links forward.
  • TF-3563 minted — new Story, TEAM-S20, "Migrate existing contacts to team_owner_ids via one-off backfill job (CHG-004)", parented to Epic TF-3185. Carries the RFC §1 Success Criteria #5 (≥95% non-empty team_owner_ids post-migration) as its acceptance criteria.
  • TF-3564 minted — new Task, same scope/AC as TF-3548, parented to Epic TF-3185 and split from TF-3563 (Work item split, verified correct direction — Task renders "split from" Story).

Consequences​

  • rfcs/rfc-team-owner-field-and-team-permission.task-breakdown.md — chunk 11's mapping row now points at TF-3564/TEAM-S20; the "Scope additions beyond the RFC" section lists TEAM-S20 alongside TEAM-S18/TEAM-S19-NEG; the ticket↔story cross-check table and summary counts updated to 3 post-RFC-scope tickets.
  • No change to the underlying risk this backfill addresses. RFC Success Criterion #5 (≥95% coverage) and the RFC review's priority action (run on a QA tenant before cdp_team_permission_enabled GA) still apply in full — TF-3564 must still be executed; closing TF-3548 did not complete the work, only re-wired its tracking.
  • No effort, staffing, QA-lane, or roadmap rank fields change as part of this decision — this is a Jira-alignment/traceability fix, not a scope or schedule change.