-
Task
-
Resolution: Fixed
-
L3 - Default
-
3.0.0
Context:
We have several user task reports (view user task) where we can group by flow node and distribute by assingee or group by assignee and distribute by user task. However, here the flow node grouping actually also refers to user tasks as well which are confusing to the user. The reason why we kept the flow node in the group by list was that we wanted to keep the number of options in the group by list to a minimum. Because consistency is more important than option reduction we should adjust this behavior.
AT:
- there is an additional entry in the group by dropdown called user tasks
- the new group by option can only be combined with the view user task
- the flow node can't be combined with the user task view any longer
- ensure consistent use of "FlowNode" and "UserTask" in all related classes, they should no longer be synonymous
This is the controller panel for Smart Panels app
1.
|
Back-end: Add group by user task option to the report builder |
|
Done | Unassigned |
2.
|
Front-end: Add group by user task option to the report builder |
|
Done | Unassigned |
[OPT-3203] Add group by user task option to the report builder
| Remote Link | New: This issue links to "Page (camunda confluence)" [ 13974 ] |
| Description |
Original:
*Context:*
We have several user task reports (view {{user task}}) where we can group by {{flow node}} and distribute by {{assingee}} or group by {{assignee}} and distribute by {{user task}}. However, here the flow node grouping actually also refers to user tasks as well which are confusing to the user. The reason why we kept the flow node in the group by list was that we wanted to keep the number of options in the group by list to a minimum. Because consistency is more important than option reduction we should adjust this behavior. *AT:* * there is an additional entry in the group by dropdown called {{user tasks}} * the new group by option can only be combined with the view {{user task}} * the {{flow node}} can't be combined with the user task view any longer |
New:
*Context:*
We have several user task reports (view {{user task}}) where we can group by {{flow node}} and distribute by {{assingee}} or group by {{assignee}} and distribute by {{user task}}. However, here the flow node grouping actually also refers to user tasks as well which are confusing to the user. The reason why we kept the flow node in the group by list was that we wanted to keep the number of options in the group by list to a minimum. Because consistency is more important than option reduction we should adjust this behavior. *AT:* * there is an additional entry in the group by dropdown called {{user tasks}} * the new group by option can only be combined with the view {{user task}} * the {{flow node}} can't be combined with the user task view any longer * ensure consistent use of "FlowNode" and "UserTask" in all related classes, they should no longer be synonymous |
| Mentioned Roles |
| Mentioned Groups |
| Labels | Original: report_builder | New: current_release report_builder |
| Assignee | Original: Sebastian Bathke [ sebastian.bathke ] | New: Johannes [ johannes.heinemann ] |
| Labels | Original: current_release report_builder | New: next_release report_builder |
| Status | Original: Open [ 1 ] | New: In Specification [ 10000 ] |