-
Type:
Sub-task
-
Resolution: Done
-
Priority:
L3 - Default
-
Affects Version/s: None
-
Component/s: backend
-
None
AT:
- using the rest-api I can evalute user tasks such that the frequency is grouped by assignee/candiate and distributed over user tasks
- the distribution can be be configured with an additional configuration option
- the new configuration field distributedBy is added to the configuration, which can have the entries none and userTask, whereby none is the default option
- this new report type should not be combinable
- the new configuration parameter is added to the rest api
- the upgrade script is adjusted so that it contains the new configuration parameter
Hints:
- make sure that filtering of user task flow nodes still work
- csv export should work as well for those reports
- isComplete needs to work