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

Assignee/CandidateGroup Filters should always filter for userTasks only

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 3.6.0-alpha1, 3.6.0
    • None
    • backend, testing
    • None
    • Not defined

      Context:

      Currently, if users create a flowNode report and apply assignee/candidate group filters, these filters apply to all flownodes. Flownodes which cannot have an assignee (gateways, service tasks etc) always count as "unassigned". 

      After discussion, it was decided to adjust this behaviour for viewLevel assignee/candidate group filters: if the filter is applied on viewLevel, an additional "userTask only" filter should be applied in the BE as well, so that the result always only includes userTasks. 

      Instance matching should work as usual: include only those instances where at least one flownode matches the filter.

      AT:

      • Assignee and CandidateGroup filters on viewLevel always apply an additional userTask only filter

       

        This is the controller panel for Smart Panels app

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

                Created:
                Updated:
                Resolved: