The identity filters are now applicable at both instance and view level. However, the view level filtering only has an effect for user task reports. We should change the implementation of the view level identity filters so that they also have an effect on flow node reports.

Hint: The identity information is stored as part of the user task rather than the flow node itself

Discussed with Felix regarding expected treatment of non userTask flownodes:
If the report is a userTask report, the identity filters should only apply to userTasks. If the report is a flowode report, they apply to all flowNodes (even if no assignee is possible due to non userTask flowode type). This also requires some adjustment of the current filter behaviour for FlowNode reports. Currently, any identityFilter also requires the flownodeType userTask, so that eg a FlowNode report with only non usreTasks and an instance identity filter for "unassigned" returns nothing, when it should return all flowNodes. Will need to check if this can/needs to be adjusted with this ticket as well.

A similar behaviour can be observed for view level flownode status filters on userTask reports, when they are applied during instance filter matching they currently do not add the userTask type filter, so that eg a completedFlowNodesOnly filter does not filter out an instance that has no completed userTasks if this instance has other completd flowNodes. This should also be adjusted

ATs:

• View level identity filters can be applied to flow node view reports
• Only the flow nodes with the identity filter matching will be returned
• behaviour of flowNode view filters on userTask reports is adjusted as described above
• Adjust docs