Extend sequenceDefinition of consecutiveShiftsWorkedRules to includeShiftTags
under review
B
Bernardo Quiroga
As discussed with Luciana:
A couple weeks ago we talked about the consecutive shifts worked rule and how it did not yield the desired result from a business point of view.
We would like to go ahead with the proposed change to scope the sequence definition to shift tags similar to how MIN_SHIFTS_WORKED_CONSECUTIVELY works.
Currently a shift from 9:30 - 18:00 is accepted as part of the sequence because it starts less than 32 hours from the shift 23:00 - 07:00. This is not desired because it is not a night shift. There should be 48 hours of rest after the 23:00 - 07:00 shift in this instance.
If I remember correctly all that is necessary to achieve the desired result is to have the sequenceDefinition be scoped by shift tags.
As mentioned above this has been discussed with Luciana and we refer to her for any details.
Log In
Brecht De Moor
updated the status to
under review
Hi Bernardo,
Thanks for submitting your feature request, and for the detailed writeup!
I want to confirm I've got it right: once a sequence starts with shifts of a specific tag (like "night"), only shifts sharing that same tag should be able to continue it. A shift with a different tag would break the sequence, even if it starts within the current time window. Let me know if I misunderstood the request.
I'll keep the status updated on the feedback board as it moves forward.
Thanks again,
Brecht
Product Manager
B
Bernardo Quiroga
Brecht De Moor
Hi Brecht,
You are correct.
Thanks for picking this up!
With kind regards,
Bernardo