-
Bug Report
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
-
Not defined
Context:
During release testing we encountered an issue with a misconfigured KPI report that was still returned by the KPI service despite having no target enabled. While users should not be able to create KPI reports in the UI with target disabled, it is potentially still possible that those reports are created by templates or imports. To ensure those reports are not treated as true KPI reports, the KPI service should not only filter on the `isKPI` flag of reports but also for the target configuration itself to be enabled.
AT:
- Reports where the `isKPI` flag is true yet the target itself is disabled should not be returned by the KPIService as KPI reports
Hint:
- filtering occurs in `KPIService.getKPIsforProcessDefinition`
- See slack convo: https://camunda.slack.com/archives/CNSMT82SJ/p1680698031910169?thread_ts=1680687349.754369&cid=CNSMT82SJ
Testing Notes:
- create a report where the target is disabled but the kpi flag is enabled
- confirm that this report is not shown as a KPI report on the processes page{}
This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10574. Please use this link for any future references and continue any discussion there.