Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-1337

I can see the relative value for count view reports

    Details

    • Type: Feature Request
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2.0-alpha1, 2.2.0
    • Component/s: frontend
    • Labels:
      None

      Description

      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

        Issue Links

          Activity

          Hide
          johannes.heinemann Johannes Heinemann added a comment -

          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.
          Show
          johannes.heinemann Johannes Heinemann added a comment - 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.
          Hide
          sebastian.stamm Sebastian Stamm added a comment -

          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.

          Show
          sebastian.stamm Sebastian Stamm added a comment - 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.
          Hide
          johannes.heinemann Johannes Heinemann added a comment -

          That's fine with me as well

          Show
          johannes.heinemann Johannes Heinemann added a comment - That's fine with me as well

            People

            • Assignee:
              Unassigned
              Reporter:
              sebastian.stamm Sebastian Stamm
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: