[OPT-1337] I can see the relative value for count view reports Created: 18/Jul/18  Updated: 18/Apr/19  Resolved: 25/Jul/18

Status: Done
Project: Camunda Optimize
Component/s: frontend
Affects Version/s: None
Fix Version/s: 2.2.0-alpha1, 2.2.0

Type: Feature Request Priority: L3 - Default
Reporter: Sebastian Stamm Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
is related to OPT-1354 I can see the relative share of a flo... Open


For the following reports:

  • Count Process Instance Frequency, grouped by Start Date
  • Count Process Instance Frequency, grouped by Variable
  • Count Flow Node Frequency, grouped by Flow Nodes

For every entry, in addition to the absolute number, I can see the relative number, which is calculated by (absoluteNumber / processInstanceCount).

The relative value is visualized in the following way:

  • For tables: A third column
  • Bar/Area/Pie Chart: In the tooltip when hovering over an entry
  • Heatmap: In the tooltip when hovering over a flownode

Comment by Johannes Heinemann [ 20/Jul/18 ]

Works like a charm

Minor review hints:

  • Could you please create a follow up ticket for the remaining view entries?
  • Heatmap.test.js/Chart.test.js/Tables.test.js: if a developer just has a look at the new test, he might not understand where the 12.3% value is coming from. I would move the value in a constant and call the constant where the value is being used.
Comment by Sebastian Stamm [ 23/Jul/18 ]

The way jest does the hoisting of the mocks, it is impossible to access out of scope variables. So I moved the mock value to the tests that are checking the value in the assertion.

For the remaining view entries, I created OPT-1354. I don't think the relative value is useful for the average process instance duration, so it's only the flow node duration views left.

Comment by Johannes Heinemann [ 25/Jul/18 ]

That's fine with me as well

Generated at Wed Oct 23 07:39:15 CEST 2019 using JIRA 6.4.6#64021-sha1:33e5b454af4594f54560ac233c30a6e00459507e.