Details
-
Type:
Feature Request
-
Status: Done
-
Priority:
L3 - Default
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 2.4.0, 2.4.0-alpha2
-
Labels:
Description
AT:
- New View selection entries:
- User Task
- Idle time (Start Time - First Claim Time): we calculate work time also if we have unassign in between
- Work time (First Claim Time-End Time): we calculate work time also if we have unassign in between
- Total time (Start Time-End Time)
- User Task
- Visualize as: table, bar, heat
- metrics to implement: min,max,avg,median (while avg is highest priority due being the default in first iteration)
- we add to docs that we use first claim time and that reassigns are not reflected in the metrics
Attachments
Issue Links
- depends on
-
CAM-9523 Using the Optimize Rest-API I can retrieve the running/completed historic task instances
-
- Closed
-
1.
|
User Task import |
|
Done | Unassigned |
2.
|
User task work-/idle-/totalTime reports |
|
Done | Unassigned |
3.
|
Integration & unit tests for user task import |
|
Done | Unassigned |
4.
|
User Task Cleanup |
|
Done | Unassigned |
5.
|
User Task report filters |
|
Done | Unassigned |
6.
|
Add new view options |
|
Done | Unassigned |
7.
|
Treat missing idle/workduration values |
|
Done | Unassigned |
8.
|
Make target values work for user task heatmaps |
|
Done | Unassigned |