Skip to main content

CDP Sprint 1 (2026-Q3) — Jira reconciliation, pass 7 (2026-07-16)

Jira reconciliation — recheck (2026-07-16, pass 7)​

Seventh pass, run via sprint:reconcile (qontak-docs, npm run sprint:reconcile -- --team cdp --json) with a full jira:digest --sprint 21382 --epic-map --vitals --since 2026-07-14. Sprint 21382 has grown from 71 to 72 issues since pass 6. Flow vitals: 22 WIP, 24 done, 13 done since 2026-07-14 — the busiest 48 hours of the sprint so far. Oldest in-progress items unchanged: Ghozi's Export BE Tasks 2.1–2.3 (TF-3284/3285/3286), now 22 days old, still touched daily (updated today).

Status of prior findings (by id) — re-verified against the 2026-07-16 digest + engine worklist:

  1. F-1 coverage-gap — STILL OPEN (7th pass), partially resolved: Create Ticket (TF-3359) still 1 QA-only issue (TF-3495 Done), 0 BE/FE. Legacy Migration Activity Logs (TF-3182) still 4 sprint issues — TF-3465 (Task 2) now READY TO DEPLOY (was In Review pass 6), but Tasks 3–9 (TF-3466–3472) still absent from this pull. Owner: TPM (Jira board edit).

  2. F-2 off-plan-load TF-3477 — ⛔ RESOLVED (7th pass): the cdp/adhoc-q3-2026/README.md bucket stood up 2026-07-14 per roadmap, backfilling 4 items already in flight. Engine 2026-07-16 correctly recognises TF-3477 as a tracked epic (5 items: 4 Done, 1 RTD in TF-3478). The July 14 Deviations amendment also re-homed TF-3499 from TF-3477 → TF-3500. However a new off-plan-load signal supersedes this: the PM/DRI Zhelia Alifa is now on the board (TF-3478, padding fix, READY TO DEPLOY) without a roster.json entry or capacity.md row — see F-10 below. Closing F-2 as resolved; F-10 is the new carrier.

  3. F-3 data-quality TF-3459 — STILL OPEN (7th pass): Won't Fix/Done, epic-less duplicate of TF-3464, engine correctly 0-credits it again (code-evidence-gap row). Owner: TPM (Jira hygiene — delete or close as duplicate, no repo action).

  4. F-4 coverage-gap CEBE RFC-authoring — ⛔ ESCALATED (open 7 passes): zero TF-3302 issues in the 2026-07-16 digest. Owner: Julio Jeffer / PM — 7 passes with no board movement is definitive signal CEBE is de facto not being worked this sprint. Proposed decision from pass 6 still stands: file the lightweight Jira Task, or record explicit not-started in Deviations.

  5. F-5 status-progress Team Owner task-breakdown missing — ⛔ ESCALATED (open 7 passes): rfcs/rfc-team-owner-field-and-team-permission.task-breakdown.md still absent from the repo (confirmed by directory listing). 18 Jira issues now exist under TF-3185 (14 To Do, 3 indeterminate/FE in-flight, 1 QA Done). Sprint is 9 of 14 days elapsed (07-16 of 07-07→07-21). Owner: Ghozi / DRI — the Jira-side breakdown already exists; this is a mechanical reverse-derivation, not new estimation work.

  6. F-6 assignment-drift Jeffer — STILL OPEN (engine false positive, 7th pass): the known sprint-reconcile.mjs casing/nickname bug persists — the engine bypasses roster.json's displayName join (Julio Jeffer Maliangkay → Julio Jeffer) on the assignment-drift check path. README implementors: already lists Jeffer correctly. No repo edit needed; upstream fix pending in qontak-docs. No new assignments drifted this pass.

  7. F-7 status-progress TF-3506 Mention User Mobile out-of-scope — STILL OPEN (2nd pass): TF-3506 Done 2026-07-14, code-corroborated per pass 6 (mobile-qontak-crm PR #1866), but rfc-notes-mention-user.task-breakdown.md line 11 explicitly excludes Mobile. 0 man-days credited. Now 2 passes old → escalate: owner DRI/PM — retro-cost into the breakdown or declare out-of-band. Extended inaction risks this staying a perma-uncounted 1.5 Mobile days.

  8. F-8 scope-watch Segmentation hardening — STILL OPEN (2nd pass): TF-3507/3508/3511 (datamart healthcheck, configurable table name, consts) are all now READY TO DEPLOY (were In Review pass 6) — still no task-id join to the breakdown, still unpriced. The P1 commitment (2026-07-28) is 12 days away with these 3 BE items in a nearly-Done state and FE tasks TF-3399/3400 now Done — the hardening work appears to have landed without disturbing the FE lane. Now 2 passes old → escalate: owner DRI — confirm these are in-scope hardening (retro-cost into the breakdown) and that the protected commitment hasn't silently grown.

  9. F-9 informational Izzul — recurs again, still expected (0 sprint issues, benched backup QA).

New findings from the 2026-07-16 engine + digest run (3 findings: 1 deterministic from engine, 2 editorial from digest analysis):

  1. F-10 off-plan-load (deterministic, engine-emitted) — Zhelia Alifa (PM/DRI) has sprint work assigned: TF-3478 ("[CDP] Fix padding on create/edit Customer Properties modal", READY TO DEPLOY, TF-3477 adhoc bucket). She is not in cdp/delivery/roster.json and has no row in cdp/delivery/capacity.md. This is real tracked load the plan doesn't surface — unlikely to threaten any ranked-initiative capacity (PM work is a separate pool), but it means any capacity.md or roster.json consumer that enumerates the CDP assignee-set misses this assignment. Owner: TPM — add Zhelia to roster.json (discipline: PM) or record in capacity.md as deliberately out-of-band management capacity that doesn't compete with engineering allocation.

  2. F-11 status-progress (editorial, real movement, major) — Customer Segmentation (P1): Azani's FE tasks TF-3399 (SegmentStore integration tests) and TF-3400 (SegmentListPage integration tests) are both Done + code-corroborated (qontak-customer-fe, resolved 2026-07-15). TF-3401 (reachability fields) is Blocked. This is the first real FE build progress beyond QA test-case writing — with the BE hardening (TF-3507/3508/3511) RTD and the FE tests landed, the 07-28 commitment has materially better odds than a week ago. Proposes a new dated status/ burnup entry (see downstream propagation worklist).

  3. F-12 status-progress (editorial, real movement, major) — Mention User in CDP Notes (P2): 13 done-since-07-14 across BE, FE, and Mobile — the single largest acceleration in any CDP sprint pass this quarter:

    • BE (Berlianto): TF-3325 (note doc model), TF-3326 (mention parser), TF-3327 (HTML sanitizer) all Done 2026-07-15, code-corroborated (contact-service). TF-3328 (active-user validation), TF-3329 (wire create/update) both READY TO MERGED. TF-3330 (notification client) In Progress.
    • FE (Jovi): TF-3331 (wire composer/renderer) READY TO DEPLOY; TF-3382 (preview-card user detail) READY TO DEPLOY. TF-3509 (deleted-user fallback) new, To Do.
    • Mobile (Alfi): TF-3290 (mention encoding), TF-3291 (data layer), TF-3294 (unit tests) all Done 2026-07-15, code-corroborated. TF-3292 (flag gating verify) Done 2026-07-16 (no code trace — verification task). TF-3293 (notification tap-through) Done 2026-07-16 (no code trace — verification task). TF-3506 (list-picker pagination) Done 2026-07-14 (F-7, out-of-scope).
    • QA (Hendry): TF-3489 (test cases) Done 2026-07-09 (prior pass, already credited). Proposes a substantial new dated status/ burnup entry (see worklist).

  4. F-13 status-progress (editorial, first signal) — Export Customer Data with Layout (P3): TF-3512 ("[FE] Expose component ExportCustomerDrawer", Jovi) Done 2026-07-15, code-corroborated (qontak-customer-fe). First non-QA progress on this initiative — the 5 BE tasks (TF-3284–3288, Ghozi) are all READY TO TEST (22 days old), and Jovi's FE export-history/report work (TF-3429/3430) is In Progress. The pipeline is close to its first end-to-end integration window. Proposes a new dated status/ burnup entry (see worklist).

  5. F-14 code-evidence-gap (editorial, 3 items) — three Mention User Mobile verification tasks Done with no code trace, all partial-search (could not reach notification-service / hub): TF-3292 (flag gating verify), TF-3293 (notification tap-through), TF-3506 (list-picker pagination — F-7, already flagged out-of-scope). TF-3292 and TF-3293 read as manual verification/QA tasks (no code change expected); TF-3506 was corroborated pass 6 but is excluded from Mention User's breakdown scope. All correctly 0-credited in the step-6b sum — informational only, no action unless a dispute arises. Also TF-3484 (TF-3477 adhoc, Ghozi, rate-limiter handling) Done, no code trace — bucket item, buckets use story-count rollup not man-days, so no propagation needed.

  6. F-15 code-evidence-gap — same 5 QA-authoring tickets (TF-3489/3490/3491/3494/3495) + TF-3459 (Won't Fix duplicate) — unchanged pattern, all correctly uncredited. Informational, no action.

What moved vs pass 6 (the headline): 13 items Done in 48 hours. Mention User's entire BE chain (parser → sanitizer → model), the FE composer+renderer+preview-card, and Mobile encoding+data-layer all landed in a single burst — Berlianto, Jovi, and Alfi's lanes all unblocked simultaneously. Customer Segmentation's FE integration-test pair landed (Azani). Export got its first BE-mirrored FE component. The sprint goal — protect the 07-21 Segmentation commitment — is materially closer now: TF-3399/3400 Done, BE hardening RTD, only TF-3401 (Blocked) remains on the FE critical path.

This pass does not fix: F-1 (sprint-scope gaps — Jira board edits needed), F-4 (CEBE RFC-authoring — PM/DRI decision still pending), F-5 (Team Owner task-breakdown — Ghozi/DRI action), F-7 (TF-3506 scope question), F-8 (Segmentation hardening pricing). F-10 (Zhelia roster entry), and F-11/F-12/F-13 (status-progress writes — proposed below, hand-applied on confirmation — no man-day credit clears the step-6b join bar until these are written).

Downstream propagation worklist (pass 7)​

#FindingCanonical artifact to reconcileOwning tool / skill
10Zhelia Alifa off-plan-load (TF-3478)cdp/delivery/roster.json + cdp/delivery/capacity.mdTPM hand-edit, then lint:delivery
11Segmentation: TF-3399/3400 Done + code-corroborated (FE 3d)cdp/customer-segmentation/delivery/status/2026-07-16.md progress_* → README cache → roadmap mirrorhand-edit status/ + lint:delivery
12Mention User: BE 3 tasks + FE 2 + Mobile 3 Done (7 code-corroborated Dones)cdp/notes-mention-user/delivery/status/2026-07-16.md progress_* → README cache → roadmap mirrorhand-edit status/ + lint:delivery
13Export: TF-3512 (FE 1d) Done + code-corroboratedcdp/export-customer-data/delivery/status/2026-07-16.md progress_* → README cache → roadmap mirrorhand-edit status/ + lint:delivery
7TF-3506 Mention User Mobile out-of-scope (2nd pass — escalated)DRI/PM decision: retro-cost or out-of-bandDRI / PM
8Segmentation hardening TF-3507/3508/3511 RTD, unpriced (2nd pass — escalated)DRI scope-check the P1 commitmentDRI review
4CEBE RFC-authoring — 7 passes untracked (escalated)File Jira Task, or record explicit not-started in DeviationsPM decision / Julio Jeffer
5Team Owner task-breakdown — 7 passes missing (escalated)Run rfc-task-breakdown against filed Jira breakdownGhozi / DRI
1Sprint-scope gaps (Activity Logs Tasks 3–9, Create Ticket BE/FE)Jira board: add TF-3466–3472, TF-3426–3428 to sprint 21382TPM (Jira board edit)

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