• Not defined

      Context:

      Currently, identity and flownode duration view level filters cannot be properly applied to incident reports and incident filterse cannot be applied to flownode/usertask reports due to the nature of our data structure where flownode and incident data are sibling nested documents within the process instance index. One way to resolve this limitation is to move incident data into the flownode data.

      However, we first need to evaluate if incidents can always be reliably associated with a specific flownode.

       

       

        This is the controller panel for Smart Panels app

            [OPT-5131] Spike: Investigate moving incident data to flownode data

            This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10807. Please use this link for any future references and continue any discussion there.

            Omran Abazeed added a comment - This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10807 . Please use this link for any future references and continue any discussion there.

              Unassigned Unassigned
              helene.waechtler Helene Waechtler
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: