KPI Sync
Date: 2025-05-09 · Duration: 62.779998779296875 min Organizer: Nader Attendees: Ahmad, Martin, Nader
Summary
-
Ahmadreza confirmed KPI program functionality after resolving issues with Martin. He will define separate Jinja template options for each KPI but will batch related issues for efficiency, improving managing workload.
-
Consensus reached to hardcode standard card types in a utility file for maintainability. Modular code discussions led to a decision to defer refactoring until more KPIs are implemented, ensuring resources are focused effectively.
-
Ticket management highlighted the need for a dedicated testing route for KPI widgets, alongside existing support tickets for Raymond. Identified ticket 323 (design for filters) as critical for frontend widget implementation, ensuring dependencies between backend and design are clarified for smooth progress.
Action Items
- Martin Elias Costa Review and merge the SQL KPIs pull request submitted by Ahmadreza Abdoli to complete ticket #11 (59:05)
Ahmadreza Abdoli Implement the Jinja template version for the card decline rate KPI as an example for Raymond and others to use (57:53) Create a new ticket to implement Jinja template versions for all KPIs (not just card decline rate) (01:01:58) Create individual tickets for each additional KPI that needs a Jinja template implementation after the card decline rate example is complete (01:01:58)
Nader Atrchin Update ticket dependencies to ensure that analytics widget front-end implementation (ticket 301) is blocked by the design task (ticket 323) (54:01) Add a comment to the analytics widget front-end ticket specifying that the KPI config file example should be renderable and used as a reference for Raymond (55:48)