Have assigned and unassigned shiftGroups as separate KPIs in run overview
L
Luciana
When sending input files with shiftGroups, it would be useful to see how many shift groups have been successfully assigned, separate from individual shifts. ShiftGroups want to have unassigned shifts left at the end of the optimisation, so it is not useful to show these unassigned shifts with the rest of the (non-group) unassigned shifts - it is more confusing when trying to work out the performance of the solver. Therefore, it would be useful to separate the shifts from shift groups in the KPIs so they can be seen at a glance, as follows:
- pinned shifts
- assigned shifts (not including shift groups)
- unassigned shifts (not including shift groups)
- assigned shiftGroups (where any one shift in the group has been assigned)
- unassigned shiftGroups (where no one shift in the group has been assigned)
Issue created due to customer feedback.
Log In