L3 - Default Based on the new identity link imported history data (which includes for example entries of operation type 'add' when a user claims a task and 'delete' when a user unclaims a task) it is possible to calculate the exact idle and work times.
Previously this idle and work time was calculated with only taking the first Claim into account.
AT:
- the exact idle and work time for user tasks is being calculated
Context For Testing:
Previously, usertask duration calculations only took into account the very first claim date. Everything between start and first claim date was counted as idle time and everything between first claim date and end was counted as work time, even if there were further unclaim/claim operations in between. Ie the work and idle times of these two userTasks would be the same, assuming the endDate and first claim happens at the same time in both cases (ignore the strikethrough, I cant figure out how to format correctly) :
Start -1> claim --2-> end
Start -1> claim --2> unclaim --3> claim --4-> end
With the new calculations, all the timeslots the usertask is unassigned is counted as idle time (1 + 3) and all the timeslots the userTask is assigned is counted as work (2 + 4).
The following exception exist:
Start --> End (completed): All time is work time, idle time is 0. The assumption is that tasks are "worked on" programmatically. Note that if the userTask is cancelled (Start --> End, cancelled), all time is idle time and work time is 0.