Skip to main content

BOT-4727 parented to the wrong Epic

Context​

BOT-4727 — [FE] Add field-array element support for dynamic field picker in ActionIntegrationForm (Task, Done, Baghiz Firdausa) — is currently parented to Epic BOT-4662 "26Q3 Chatbot - CRM Actions: Custom Fields". That Epic is wrong for this work, so the Epic ⇄ Story ⇄ Task alignment for this task does not reflect reality.

Notes​

  • Task: BOT-4727, created 2026-07-22, status Done, assignee/reporter Baghiz Firdausa.
  • Current parent: Epic BOT-4662 (In Progress, Medium - P2).
  • Scope of the task: new ActionFieldArrayField.vue popover picker, an html.element = "field array" branch in ActionIntegrationForm.vue, and extending the six "select multiple" guards in useActionFormHandler.ts to also match "field array".
  • Correct Epic: BOT-4790 — "26Q3 Chatbot - CRM Actions: Get Ticket & Get Deals", minted 2026-07-27 (Hilmi Muktitama). The originating work is the Jun 17 "get ticket / get deals" AI Agent actions thread (below), not CRM Custom Fields.

Origin — Google Chat thread, Jun 17 (room link)​

  • Dimas Fauzi Hidayat raised the need for get ticket and get deals AI Agent actions.
  • Get ticket uses the get all tickets endpoint, searched by the ticket id (string, e.g. 164RICTORP) — not the numeric id and not unique_deal_id. CRM now has a native ticket feature, so renaming deals into tickets is no longer needed: https://api.mekari.com/qontak/crm/tickets?unique_ticket_id=164RICTORP
  • Eko Aprianto: for get ticket / get deals the only parameter should be the ticket number (input text), and this is a BE adjustment — but the user must also be able to pick which fields to share from the available fields (Dimas), and at that time "FE belum bikin dynamic komponen yang kaya di Figma" — only the room-tag style multi-select existed. That missing dynamic field picker is exactly what BOT-4727 built (ActionFieldArrayField.vue).
  • Send image/attachment was the third action in the batch; it differs because FE needs a file component.
  • Figma: get ticket · get deals — Dimas noted the design still needs tweaks.
  • Scheduling: get ticket and get deals were deferred to the following sprint and parked in the Sprint 7 backlog; the priority list discussed was (1) Chatbot Basic handling HMAC, (2) Google Native integrations, (3) AI Agent action to send image attachments, (4) continue Autonomous, (5) Chatcommerce (blocked on a missing icon and on new endpoints from Chat), (6) cron to run AI Agent scenarios automatically — with the tickets/deals work slotted around no. 6.
  • The thread also agreed to record these actions in the documents repo and to complete the documentation of available / todo / in-progress actions.

Decisions / changes​

  • 2026-07-27, Hilmi Muktitama: minted child Epic BOT-4790 "26Q3 Chatbot - CRM Actions: Get Ticket & Get Deals" under the qontak-action umbrella BOT-4597, and re-parented BOT-4727 from BOT-4662 to BOT-4790.

  • Filed the Story and Task family under BOT-4790, all To Do and unassigned:

    KeyTypeSummary
    BOT-4791StoryGTGD-S01 — Get Ticket action: look up a ticket by ticket id and share selected fields
    BOT-4792StoryGTGD-S02 — Get Deals action: look up a deal and share selected fields
    BOT-4793Task[GTGD] Task 1 — [BE] Get Ticket action: node registry entry + lookup by unique_ticket_id
    BOT-4794Task[GTGD] Task 2 — [BE] Get Deals action: node registry entry + deal lookup

  • Split links created (Work item split, Task → split from → Story, verified on the first link): BOT-4793 ← BOT-4791, BOT-4794 ← BOT-4792, and BOT-4727 ← both BOT-4791 and BOT-4792 (the field picker serves both actions).

  • BOT-4790 registered in the initiative README ## Jira Epics allow-set and ## Action catalog.

  • Swept BOT-4662's other 24 children: all are genuine QACF custom-fields work; BOT-4727 was the only mis-parented one.

Follow-ups​

  • Delete the stale link BOT-4664 split to BOT-4727 (link id 438185) — the MCP toolset has no delete-link operation, so this must be removed by hand in Jira — TBD.
  • Assign BOT-4793 / BOT-4794 and size them at sprint planning — TBD.
  • Confirm the deal lookup parameter for GTGD-S02 with Dimas Fauzi Hidayat; the Jun 17 thread only settled the ticket case — TBD.
  • Write the Get Ticket & Get Deals PRD (write-prd) and back-fill ACs onto BOT-4791 / BOT-4792 — TBD. The Stories carry the thread's scope notes but no acceptance criteria yet.
  • Confirm the Figma designs after the tweaks Dimas flagged — TBD.
  • Add BOT-4790 to the roadmap / capacity mirrors once the work is scheduled — TBD.