Details
-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
Description
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