Skip to main content

Bifrost Sprint 1 (2026-Q3) — Jira reconciliation, pass 1 (2026-07-07)

Jira reconciliation (2026-07-07)​

Checked this sprint's plan against the actual state of Jira sprint 21367 ("Bifrost 26Q3 Sprint 1", jira_sprint_id above). Findings, most-material first:

  1. One CID Multiple WABA (BIF-6428, P11) shows status: Done / resolution Done in Jira, conflicting with Grehasta #3, Syafrizal M. #6, and Izzul #2 all still treating it as open work this sprint (flagged inline on those rows above). Either the Epic was closed in error, or the initiative is actually finished and those three rows are stale. Needs PM/TPM confirmation before more BE/FE/QA time is spent on it — not resolved by this edit, only surfaced.

  2. Jira sprint 21367 only has issues scoped for 2 of the 16 initiatives in the index table above — Deduction V2 (BIF-8644, 8 items, all on Hafriz, matching his queue) and Self Top-up (BIF-7797, the 6 retest bugs). The other 14 initiatives this plan marks Ready/active this sprint (P2, P4–P16) have zero corresponding Stories/Tasks pulled into the Jira sprint. P2 (Meta WhatsApp Pricing) now has a task-breakdown (12 md, authored 2026-07-06) but is still unstaffed, with Madani only reviewing/building its Phase-1 tasks — and P4–P16 having nothing on the board is real drift between this written plan and what Jira actually shows as committed. Not resolved here; someone needs to pull the relevant Stories/Tasks into sprint 21367 for the queues that are genuinely starting.

  3. Self Top-up retest bugs (BIF-8704–8709) were unassigned in Jira despite this doc originally saying "Madani owns the fix." Triaged by FE/BE and assigned 2026-07-07: BIF-8704/8705/8706/8707 → Syafrizal M. (FE display/interaction bugs), BIF-8708/8709 → Madani (BE seed-data/component-gating bugs, per the precedent in self-topup.task-breakdown.md). Reflected in Madani's #2 and Syafrizal M.'s new #11 above. Medium confidence on 4 of the 6 (8705/8706/8708/ 8709) — reassign if whoever picks it up finds it's actually the other layer.

  4. Syafrizal M. carries 6 additional open Jira items with no home in this plan: 1 task under BIF-7803 (26Q2 Adhoc Request), 2 tasks under BIF-8101 (26Q2 Internationalization – Conversation SLA, itself still In Progress), and 3 unparented tasks (BIF-8691/8692/8693) — none map to any of the 16 tracked initiatives. This is on top of capacity.md's existing over-capacity (1.21) flag for him, plus the 4 FE bugs from #3 above — his real committed load is higher than either this plan or capacity.md currently shows. Flagged for TPM; not descoped or reassigned here.

  5. 26Q3 Adhoc (BIF-8695) added to this sprint 2026-07-08 — its Jira Stories are not yet in sprint 21367. The Epic BIF-8695 and its 10 Stories (BIF-8682/8696/8718/8736/8747/8749/8750/8751/8787/ 8788) already exist on the board, but none is pulled into sprint 21367. Because these enter as pull-in fill rather than committed load, that is arguably correct for now — but any adhoc story an engineer actually starts should be pulled into the sprint and its Tasks created per the repo's manual Jira convention (jira-alignment-check for missing per-story wiring, then sprint-jira-sync for Tasks — never the automated per-AC sync). Also note the Stories are mirrored per-user-story already (one Story per PRD), so the Epic is correctly per-story, not per-AC. Not actioned by this edit — flagged for whoever pulls the first adhoc item.

None of items 1, 2, 4, or 5 are fixed by this edit — they're recorded here so the drift isn't lost before sprint close, per the "captures, never estimates" rule for this layer.