Cloning a shift over a pre-existing shift should not lead to overlapping shifts
When a shift is cloned over a pre-existing shift it results in overlapping shifts in the roster.
This is not expected. The expected behaviour would be that cloning over. a pre-existing shift is not allowed, similar to how manually adding a new shift to the roster where a shift already exists is not allowed.
This is a bug, but response from support is that it woks as designed?!?
Steps to reproduce:
1. Open a roster
2. Click on the Cloning Tool
3. Select an existing shift (not task) in the timeline to select it for cloning
4. Click on the location in the timeline where there is a pre-existing shift.
5. The new shift will be added on top of the existing one, leading to overlapping shifts.
1
vote
Tibi Duka-kispal
shared this idea