Skip to main content

CDP Sprint 1 (2026-Q3) — Jira reconciliation, pass 4 (2026-07-10)

Jira reconciliation — recheck (2026-07-10, pass 4)​

Fourth pass, run via sprint:reconcile against a fresh pull. Sprint 21382 has grown from 50 to 58 issues since pass 3 — real movement, not just relabeling.

Status of the 2026-07-09 (pass 3) findings, re-verified against the 2026-07-10 pull:

  1. coverage-gap (sprint-scope drift) — PARTIALLY RESOLVED: TF-3399/3400/3401 (P1 Segmentation FE), TF-3312–3316 (Team Owner FE), and TF-3271/3272/3273/3279 (Team Owner Mobile) are now correctly filed and in sprint 21382. STILL OPEN for Legacy Migration Activity Logs BE (Jeffer's Tasks 1→9, TF-3464–3472 — none of these keys appear in this pull at all, only the QA ticket TF-3493 and the TF-3459 duplicate are epic-linked to TF-3182) and for Create Ticket web track (TF-3426/3427/3428 — still absent; only the QA ticket TF-3495 is in-sprint under TF-3359).
  2. roster-mismatch (Azani zero board presence) — RESOLVED: Azani now has 8 issues in sprint 21382 (TF-3312–3316 Team Owner FE, TF-3399/3400/3401 Segmentation FE).
  3. off-plan-load (TF-3477 "26Q3 CDP Adhoc") — STILL OPEN, partial progress: of its 5 tasks, 3 are now Done (TF-3484 Ghozi, TF-3483 Jovi, TF-3486 Julio Jeffer); TF-3478/TF-3479 remain To Do, still assigned to Zhelia Alifa (off-roster). Still undocumented in the repo — no bucket README/tracker, no roadmap Adhoc-lane entry.
  4. Data-quality (TF-3459 duplicate of TF-3464) — STILL OPEN, unchanged: TF-3459 confirmed Won't Fix/Done, epic-less, still the only TF-3182 issue other than the QA ticket that resembles "done" — its Won't-Fix/duplicate status means it is not counted as real progress below.
  5. coverage-gap (Export Customer Data BE) — STILL OPEN: TF-3181 in-sprint still has only FE (Giovanni, 5 tasks incl. 2 new: TF-3378, TF-3429, TF-3430) and QA (Hendry) tickets, zero BE for Ghozi's confirmed 15-day queue item.
  6. coverage-gap (CEBE RFC-authoring task) — STILL OPEN: no TF-3302 issue of any kind in sprint 21382.
  7. status-progress (P3/Team-Owner task-breakdown not mirrored to repo) — STILL OPEN: cdp/team-owner-field-and-team-permission/rfcs/ still holds only the RFC + its review.
  8. status-progress (TF-3464 in-progress but unsprinted) — now moot for this pull: TF-3464 does not appear in the 2026-07-10 sprint-scoped digest at all (neither does the rest of Jeffer's Legacy Migration Activity Logs task range) — re-confirm against a non-sprint-scoped query before treating this as resolved-by-removal vs. a transient pull gap.
  9. Segmentation QA slice (TF-3490) / stale baseline — APPLIED IN THIS PASS (was proposed in the pass-3 worklist as item 9): see below.
  10. roster.json accountIds unresolved — STILL OPEN, unchanged.
  11. Izzul false roster-mismatch — recurs again this pass (see engine output below); still informational, no action.

New findings from the 2026-07-10 (pass 4) engine run (sprint:reconcile, 7 findings: 3 deterministic, 4 editorial):

  1. coverage-gap (deterministic): Create Ticket & Auto-Associate (TF-3359) still has exactly 1 in-sprint issue and 0 BE/FE tags (the QA ticket TF-3495) — narrower restatement of finding 1.
  2. assignment-drift (deterministic): Legacy Migration: CRM Activity Logs README implementors already lists Julio Jeffer as Backend — the engine's + julio jeffer (assigned in Jira, absent from README) signal is a false positive here (name-matching artifact against roster.json, which has his accountId still null per finding 10); no README edit needed.
  3. roster-mismatch (deterministic): Izzul has 0 sprint issues — expected per finding 11, not a gap (QA backup, intentionally benched this sprint).
  4. status-progress (editorial, ×4 — the reason for this pass): Customer Segmentation (1 done / 3 in-progress of 4 sprint issues), Legacy Migration Activity Logs (1 done / 0 in-progress of 2 — that "1 done" is TF-3459, the duplicate from finding 4, not real progress), Mention User (1 done / 2 in-progress of 16), Team Owner Field & Team Permission (0 done / 1 in-progress of 18). Re-read against each task-breakdown's man-days (not just issue counts):
    • Customer Segmentation: TF-3490 (Hendry, QA test-cases) is Done = 1.5 QA days. The three FE tasks (TF-3399 In Testing, TF-3400/3401 In Progress) map to task-breakdown Tasks 2.1/2.2/2.3 (1 + 1.5 + 0.5 FE days) but none are Done, so 0 credited. 1.5 / 8.5 known days = 18%. Applied: new dated status/2026-07-10.md, cached to README progress_* and the roadmap ## Portfolio progress & forecast row.
    • Mention User: TF-3489 (Hendry, QA test-cases) is Done = 4.5 QA days. Berlianto's 6 BE tasks are all To Do (0 credited); Jovi's 2 FE wiring tasks are In Progress, not Done (0 credited). 4.5 / 34 known days = 13%. Applied: new dated status/2026-07-10.md, cached to README progress_* and the roadmap row.
    • Legacy Migration Activity Logs: the only "done" issue (TF-3459) is the confirmed duplicate of TF-3464 (finding 4), which is itself Won't Fix — not credited as real work. No status/README/roadmap change; stays at 0%.
    • Team Owner Field & Team Permission: the sole in-progress issue (TF-3491, QA test-cases) is not yet Done — not credited. No status/README/roadmap change; stays at 0%.
  5. SPRINT_PRIORITY_DRIFT (per lint-delivery.mjs, real and new): the CDP roadmap ## Priority table was reprioritized again on 2026-07-10 — Export Customer Data moved to P3 (from P6), Team Owner Field & Team Permission to P4 (from P3), Legacy Migration: CRM Notes to P5 (from P4), Legacy Migration: CRM Activity Logs to P6 (from P5) — per export-customer-data/delivery/decisions/0001-reprioritize-bulk-export-over-team-permission.md. This sprint doc's sprint_goal, ## Initiative index, every per-engineer queue, ## Deviations, and ## The real blockers still carried the pre-reorder ranks. Fixed in this pass: every P3/P4/P5/P6 label relabeled to match the roadmap (same mechanical relabel lint-delivery.mjs caught and pass 2 fixed for P1/P2 on 2026-07-07). Relabeling exposed a genuine SPRINT_QUEUE_ORDER divergence (lint-delivery.mjs, advisory): Ghozi, Alfi, and Hendry all still queue Team Owner (P4) ahead of Export (P3), which matched rank when this sprint doc shipped but no longer does. Not auto-reordered — the reprioritization ADR itself flags Team Owner's 2026-08-31 hard date as a possible sequencing exception, not yet DRI-confirmed — documented as an open Deviation instead (see ## Deviations from roadmap priority).

This pass does not fix: the 5 still-open Jira findings (Legacy Migration Activity Logs BE sprint-scope, Create Ticket web-track sprint-scope, the TF-3477 adhoc bucket's documentation, the TF-3459 duplicate, the Export BE coverage gap, the CEBE RFC-authoring task, the missing Team-Owner task-breakdown file) — those still need the PM/TPM/DRI calls and Jira edits from the pass-1/3 worklists, unchanged by this pass. roster.json accountId resolution also remains open.

Downstream propagation worklist (pass 4 additions)​

#FindingCanonical artifact to reconcileOwning tool / skill
12Legacy Migration Activity Logs BE work (Tasks 1-9, Jeffer) still not in sprint 21382Add TF-3464–3472 (or re-file if they no longer exist) to sprint 21382 in JiraHand-edit in Jira, then re-run sprint-resync
13Create Ticket web track (Jovi, Tasks 1-3) still not in sprint 21382Add TF-3426/3427/3428 to sprint 21382 in JiraHand-edit in Jira, then re-run sprint-resync
14TF-3477 adhoc bucket now 60% done (3/5 tasks) but still undocumentedDecide: fold into a proper bucket initiative or wind down — same call as pass-1 finding 3, now more urgent given active throughputPM/TPM decision, then bucket README + roadmap ## Adhoc / Interrupt lane
15assignment-drift false positive on Legacy Migration Activity Logs README (Jeffer already listed)No repo edit; root cause is roster.json accountId: null for Jeffer (worklist item 10) — resolving that removes the false positive on the next passn/a until roster.json accountIds are resolved

Always run npm run lint:delivery (DOCS_ROOT pointed at this repo) after any propagation edit.