Skip to main content

CDP Sprint 1 (2026-Q3) — Jira reconciliation, pass 11 (2026-07-21, close pass)

Jira reconciliation — recheck (2026-07-21, pass 11 — CLOSE PASS)​

Eleventh and final pass — sprint 21382 closes today (day 14 of 14). Digest pulled via MCP (no JIRA_* creds in this session) and fed offline to sprint:reconcile --digest (qontak-docs @ 7bfdc11); step-6b progress computed; sprint review drafted and the sprint doc archived this pass.

Flow vitals: 78 → 80 issues (+2 net — TF-3537, TF-3547 added late; no pull-outs); 66 done / 13 WIP / 1 to-do; 40 issues done since 2026-07-17 (close-week wave — more than the whole first 10 days combined); oldest in-progress: TF-3283 / TF-3289 (Jovi, Export FE, created 06-24, 27d — both Ready to Test, queued behind the testing lane, not abandoned).

Progress computation (step 6b — computed, code-corroborated)​

InitiativeNewly done (joined)Days addedNew burnupEvidence
Mention User (TF-3184)TF-3328/3329/3330 = BE Tasks 2.4/2.5/2.6 (0.5+3.0+3.0)+6.517.5 / 34 = 51% (was 32%)all three merged to contact-service default (engine code:evidence, 13/16 done corroborated)
Export (TF-3181)TF-3284–3288 = BE Tasks 2.1–2.5 (1+3+2+3+2.5)+11.511.5 / 32.5 = 35% (was 0%)all five merged to contact-service default (engine corroborated)
Customer Segmentation (TF-2544)none joinable (TF-3401 not Done)04.0 / 8.5 known = 47% (unchanged)commitment-day record below
Legacy Migration: CRM Activity Logs (TF-3182)none02.0 / 24.5 known = 8% (unchanged)board 4/4 done is an F-1 artifact, see F-23

Not credited (flagged, unresolved):

  • CRM Notes (TF-3183) — TF-3407 (Task 1.1, 2.0d) Done but code only on an unmerged branch (contact-service:origin/TF-3407-…); TF-3408 (Task 1.2, 1.5d) Done with no code trace in contact-service. Both 0-credited → stays 0% (new F-20).
  • Export unjoinable done set — TF-3525 ("Task 1.5", no such breakdown task), TF-3538/3542/3547 (net-new BE APIs), TF-3512 (drawer expose, no task-id): 5 done issues outside the 26-day breakdown (new F-21, scope-watch). TF-3429/3430 (CHAT FE) Done but unmerged branches (new F-19) — 0 until merged.
  • Team Owner (TF-3185) — 13/18 done (all 12 TEAM-S BE stories + QA doc; FE Tasks 1–5 all READY TO DEPLOY). Breakdown now exists but carries no effort estimates (F-5 residual) → count-note only, stays 0%.
  • Create Ticket (TF-3359) — 1/1 done (TF-3495, QA doc, code-free). Stays 0%; zero BE/FE items ever filed (F-1).
  • Mention User Mobile — now 7 done Mobile items (TF-3290–3294, 3296, 3506) outside breakdown scope (F-7) → 0. Phase-1 FE tasks 1.1–1.4 still have no board issues (F-17).
  • Segmentation datamart hardening — now 6 done unpriced BE items (+TF-3537, chat data to S2S segment customers); F-8 grew again.
  • Adhoc bucket (TF-3477) — TF-3484/TF-3486 Done with no code trace in any registry repo (new F-22; bucket is man-day-exempt, board-fix note only). TF-3478 (Zhelia) READY TO DEPLOY.
  • QA test-case tasks (TF-3489/3490/3491/3493/3494/3495) and Mobile verification tasks (TF-3292/3293) graded no-trace are genuinely code-free — stated, not gaps.

Prior findings re-tested​

  • F-1 coverage-gap — STILL OPEN (9th pass) ⛔: CALM Tasks 3–9 (TF-3466–3472) and Create-Ticket web (TF-3426–3428) never entered the sprint. At close this converts to a carry-over input to sprint-planner (Sprint 2 must file them deliberately). Owner: TPM.
  • F-3 data-quality — ✅ RESOLVED pass 11: TF-3459 now closed Won't Fix (duplicate of TF-3464). Board hygiene done.
  • F-4 coverage-gap CEBE — STILL OPEN (9th pass) ⛔: zero TF-3302 board items all sprint; the RFC-authoring slice has no board trace and no RFC file exists. Owner: Julio Jeffer / PM — Sprint 2 must either file the authoring task or descope CEBE explicitly.
  • F-5 status-progress — ✅ RESOLVED pass 11 (with residual): rfc-team-owner-field-and-team-permission.task-breakdown.md now exists. Residual: it is a BE-only coverage mapping with no effort estimates (deliberate, per its own header), so Team Owner progress remains count-based; FE/Mobile chunks and man-day sizing still unmapped — feeds sprint-planner step 2 (Sprint 2's goal already names this).
  • F-7 Mobile retro-cost — STILL OPEN (4th recheck) ⛔: now 7 done Mobile items, 0 credited. Owner: DRI/PM — retro-cost or declare out-of-band; 4 rechecks without a decision.
  • F-8 scope-watch datamart — STILL OPEN (4th recheck) ⛔, grew: 5 → 6 unpriced done BE items (+TF-3537). Owner: DRI — confirm in-scope + retro-cost.
  • F-10 off-plan-load Zhelia — STILL OPEN (3rd recheck) ⛔: engine re-emitted (TF-3478 READY TO DEPLOY; no roster/capacity row). Owner: TPM — roster.json (discipline PM) or out-of-band note in capacity.md.
  • F-16 TF-3521 watch — STILL OPEN (watch): TF-3524 Done, still the Epic's only item; no folder/roadmap registration needed yet. Owner: TPM; revisit at Sprint 2 volume.
  • F-17 Mention FE Phase-1 backfill — STILL OPEN (2nd recheck → ⛔ ESCALATED): Tasks 1.1–1.4 (~7 FE days) still have no board issues while dependent Phase-2 work is Done/merged. Owner: TPM / Jovi — backfill via sprint-jira-sync so the burnup stops understating Mention User (real ≈ 24.5/34 if Phase 1 is de facto done).
  • F-18 engine limitation — CONFIRMED (2nd pass): the roster-mismatch "Izzul 0 issues" row is still the off-map-Epic join artifact (TF-3524 is Izzul's, Done). Upstream report to sprint-reconcile.mjs still pending — carried in Retro actions.

New findings from the 2026-07-21 pull​

  • F-19 code-evidence-gap (Export): TF-3429/TF-3430 board-Done, code only on unmerged branches (hub-chat, qontak-customer-fe). 0-credited. Owner: Jovi / TPM — merge or revert board status.
  • F-20 code-evidence-gap (CRM Notes): TF-3407 unmerged branch; TF-3408 no trace. Both 0-credited; CRM Notes stays 0% despite 2/3 board-done. Owner: Berlianto / TPM — merge or fix board.
  • F-21 scope-watch (Export): 5 done issues outside the breakdown (TF-3525, TF-3538, TF-3542, TF-3547, TF-3512) — Export scope has grown past its 26-day breakdown without retro-costing. Owner: DRI — same shape as F-8.
  • F-22 code-evidence-gap (adhoc bucket): TF-3484/TF-3486 Done, no code trace anywhere in the registry set. Bucket rollup unaffected (count-based); board-fix / declare-code-free note. Owner: TPM.
  • F-23 blocked-done-conflict (CALM): all 4 TF-3182 sprint issues Done while README health: at-risk and real progress is 2 of 17 BE days — the board is green only because F-1's Tasks 3–9 were never filed. Do not flip health from the board; recorded in legacy-migration-crm-activity-logs/delivery/status/2026-07-21.md. Owner: TPM (resolves with F-1).

This close pass does not fix: F-1/F-4 (Sprint-2 planning inputs), F-7/F-8/F-21 (DRI retro-cost decisions), F-10 (TPM roster call), F-17 (board backfill), F-19/F-20/F-22 (board/merge fixes) — each named above with its owner; all carried into the Sprint review's carry-over list.

Downstream propagation worklist (this pass — applied same-pass)​

#FindingCanonical artifact reconciledOwning tool / skill
1status-progress Mention User 51%notes-mention-user/delivery/status/2026-07-21.md → README cache → roadmapstep 6b (applied)
2status-progress Export 35%export-customer-data/delivery/status/2026-07-21.md → README cache → roadmapstep 6b (applied)
3Segmentation commitment-day recordcustomer-segmentation/delivery/status/2026-07-21.md (47% unchanged)step 6b (applied)
4F-20 CRM Notes evidence gapslegacy-migration-crm-notes/delivery/status/2026-07-21.md (0%)step 6b (applied)
5F-23 CALM board-green-vs-at-risklegacy-migration-crm-activity-logs/delivery/status/2026-07-21.md (8%)step 6b (applied)
6Team Owner BE-complete count-noteteam-owner-field-and-team-permission/delivery/status/2026-07-21.mdstep 6b (applied)
7F-1 + F-4 carry-overSprint 2 planningsprint-planner (step-2 input)
8F-17 FE backfillJira boardsprint-jira-sync
9F-19/F-20/F-22 merges / board fixesJira board + code reposassignees / TPM (board fix, never repo edit)
10F-7/F-8/F-21 retro-costingtask-breakdowns + README effortDRI
11Sprint closesprint doc ## Sprint review + status: archivedthis pass