-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
3
-
L
Context:
This task has been separated from OPT-4716. Currently, incident viewlevel fitlers cannot be properly applied to flowNode and userTask reports. Similarly, identity and flownode duration/status view filters do not work properly for incident reports due to the instance data structure keeping incidents in a separate list from flowNode data.
One way to resolve this limitation would be to merge incident and flowNode data, but currently we are not sure if this is possible as incidents may not always be strictly related to a flownodeInstance. This should first be evaluated in the spike subticket.
AT:
- Make incident view level filter work for flownode / usertask reports
- Make identity view level filters work for incident reports
- Make flow node duration and Flow node status filter work for incident reports
- Adjust docs accordingly (currently we mention this limitation somewhere)
This is the controller panel for Smart Panels app
1.
|
Spike: Investigate moving incident data to flownode data |
|
Open | Unassigned |
2.
|
Incident view level filters should work for user task reports |
|
Open | Unassigned |
3.
|
Incident view level filters should work for flow node reports |
|
Open | Unassigned |
4.
|
Flow node duration view level filter should work for incident reports |
|
Open | Unassigned |
5.
|
Identity view level filters should work for incident reports |
|
Open | Unassigned |
[OPT-5278] Apply view level filters on reports correctly - Incident filters & reports
| Labels | Original: current_release | New: potential_for_next_quarter |
| Description |
Original:
*Context:*
This task has been separated from One way to resolve this limitation would be to merge incident and flowNode data, but currently we are not sure if this is possible as incidents may not always be strictly related to a flownodeInstance. This should first be evaluated in the spike subticket. AT: * Make incident view level filter work for flownode / usertask reports * Make identity view level filters work for incident reports * Make flow node duration and Flow node status filter work for incident reports * Adjust docs accordingly (currently we mention this limitation somewhere) |
New:
*Context:*
This task has been separated from One way to resolve this limitation would be to merge incident and flowNode data, but currently we are not sure if this is possible as incidents may not always be strictly related to a flownodeInstance. This should first be evaluated in the spike subticket. *AT:* * Make incident view level filter work for flownode / usertask reports * Make identity view level filters work for incident reports * Make flow node duration and Flow node status filter work for incident reports * Adjust docs accordingly (currently we mention this limitation somewhere) |
| Mentioned Roles |
| Mentioned Groups |
| Labels | Original: potential_for_next_quarter | New: blog potential_for_next_quarter |
| Labels | Original: blog potential_for_next_quarter | New: blog potential_for_next_quarter should_have |
| Effort | Original: Not defined [ 11259 ] | New: L [ 11256 ] |
| Status | Original: Open [ 1 ] | New: Scheduled [ 10912 ] |
| Status | Original: Scheduled [ 10912 ] | New: Open [ 1 ] |