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

Flow node frequency reports return null on zero count

    Details

    • Type: Task
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.5.0
    • Component/s: backend
    • Labels:

      Description

      AT:

      • the evaluation of flow node frequency reports returns null for all flow nodes that have never been executed

      Context:
      The heatmap in the front-end distinguishes between three states:

      • a flow node has a number larger than 0
      • a flow node value is 0
      • a flow node has never been executed and is therefore null

      This is because in a duration heatmap a flow node can have a duration of zero but still has been executed. For those flow nodes with zero duration we still show a heat so that users know that those have been executed with a small duration. Hence, we need those three states. If we now return also zero for flow node frequency reports, those flow nodes will also have a heat, which is actually not what we want.

        Issue Links

          Activity

          johannes.heinemann Johannes Heinemann created issue -
          johannes.heinemann Johannes Heinemann made changes -
          Field Original Value New Value
          Description *AT:*
          * the evaluation of flow node frequency reports returns null for all flow nodes that have never been executed
          *AT:*
          * the evaluation of flow node frequency reports returns null for all flow nodes that have never been executed

          *Context:*
          The heatmap in the front-end distinguishes between three states:
          * a flow node has a number larger than 0
          * a flow node value is 0
          * a flow node has never been executed and is therefore null

          This is because in a duration heatmap a flow node can have a duration of zero but still has been executed. For those flow nodes with zero duration we still show a heat so that users know that those have been executed with a small duration. Hence, we need those three states. If we now return also zero for flow node frequency reports, those flow nodes will also have a heat, which is actually not what we want.
          johannes.heinemann Johannes Heinemann made changes -
          Link This issue is related to OPT-2263 [ OPT-2263 ]
          johannes.heinemann Johannes Heinemann made changes -
          Labels current_release next_release
          johannes.heinemann Johannes Heinemann made changes -
          Labels next_release current_release next_release
          johannes.heinemann Johannes Heinemann made changes -
          Labels current_release next_release current_release
          johannes.heinemann Johannes Heinemann made changes -
          Assignee Johannes Heinemann [ johannes.heinemann ] Kyrylo Zakurdaiev [ kyrylo.zakurdaiev ]
          johannes.heinemann Johannes Heinemann made changes -
          Status Open [ 1 ] In Specification [ 10000 ]
          kyrylo.zakurdaiev Kyrylo Zakurdaiev made changes -
          Assignee Kyrylo Zakurdaiev [ kyrylo.zakurdaiev ]
          Status In Specification [ 10000 ] Done [ 10010 ]
          Resolution Fixed [ 1 ]
          sebastian.stamm Sebastian Stamm made changes -
          Fix Version/s 2.5.0 [ 15385 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              johannes.heinemann Johannes Heinemann
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: