Skip to main content

Qontak Action (AI Agent) — Status 2026-07-16

Delivery / Program Management — periodic status report. First dated status entry for this initiative. effort_*/progress_* on the README are still TBD — this report does not resolve that; it records a board-registration gap discovered via sprint-resync.

Summary​

Sprint-resync pass 6 (2026-07-16) escalates a real, unregistered Jira Epic tied to this initiative — substantial engineering work is already underway on the live sprint board with no corresponding entry in this initiative's own docs (README Jira-Epics family table, PRD jira_epic field, or staffing).

Risk & dependency changes​

  • Escalating (sprint-resync pass 6, F-20, epic-wiring-drift, 2nd appearance since pass 5). Jira Epic BOT-4662 ("26Q3 Chatbot - CRM Actions: Custom Fields", created 2026-07-15) carries its own description pointing at this initiative's repo artifacts: PRD prds/crm-actions-custom-fields.md, backend RFC rfcs/crm-actions-custom-fields.md, frontend RFC rfcs/crm-actions-custom-fields-fe.md, and both task-breakdowns (BE 6d, FE 7d — DRI-confirmed, high/medium confidence). None of this is registered here: the PRD's own jira_epic: BOT-3350 does not match the live Epic (BOT-4662); BOT-4662 is not listed in this README's ## Jira Epics family table; and this README has no implementors: field at all, despite 3 named engineers already carrying board work.
  • Board reality vs. plan text. As of this pass, BOT-4662 has 3 BE issues Done (Eko Aprianto), 2 BE issues Ready-to-Deploy (Eko Aprianto), 1 BE issue Ready-to-Merged/in review (Agus Suparman), and 4 FE issues In Progress (Baghiz Firdausa) — 6 of 10 sprint issues functionally complete or near-complete. This directly contradicts the active sprint doc (chatbot/delivery/sprints/2026-07-13-sprint-01.md), which still lists this work as "Placeholder — CRM Deals Custom Field Support (Epic TBD)... do not start build until confirmed" for Baghiz (#1) and Agus (#2) only. Eko Aprianto, who holds 5 of the 6 BE tasks (3 already Done), has zero mention in the sprint plan for this work.
  • Decision needed from Dimas Fauzi Hidayat (PM/TPM), all at once: (1) confirm BOT-4662 as the canonical child Epic for this action group (vs. the already-shipped BOT-3350), (2) add it to this README's ## Jira Epics family table, (3) correct the PRD's jira_epic field to match, (4) add implementors: here (Eko Aprianto, Agus Suparman — BE; Baghiz Firdausa — FE), (5) replace the sprint doc's two "Placeholder — Epic TBD" rows with the real links, (6) correct the roadmap's P10 row (currently "Visible backlog only... not projected into Sprint 01" — false as of this pass). Two passes open with no response is at the escalation threshold in .claude/reference/sprint-resync.md §4.

Metrics​

  • Progress: effort_*/progress_* remain TBD on the README pending the registration decision above — this report deliberately does not invent an effort split across BOT-3350 (already-shipped) vs. BOT-4662 (new) before the DRI confirms which Epic the man-days belong to.

Next period​

  • Resolve the F-20 registration decision above — this is the single highest-leverage item this initiative can close, since real completed work is currently invisible to every planning artifact.
  • Once registered, run initiative-timeline-mapper for this initiative to produce a real forecast (currently impossible — no effort/progress on file).