-
Sub-task
-
Resolution: Done
-
L3 - Default
-
None
-
Not defined
Context:
As identified in design review the current behavior of the combination of group by user task and filter by assignee/candateGroup is not really the expected behavior for a user as all user Tasks are shown that belong to instances where at least one userTask has the filtered assignee. We instead want to only consider the exact userTasks the particular assignee is set instead of all tasks of the process instance
AT:
- on group by userTask and filter by Assignee/CandidateGroup only the userTasks with that particular assignee/candidateGroup are taken into account in the result
- for group by flow node the current behavior (returning all flow nodes belonging to a process instance were at least one usertask satisfies the assignee/candidateGroup-Filter) stays