User experiencing inconsistent planning behaviour with the same tasks sometimes pushing forwards and sometimes pushing back, when being dragged on the plan.
User has two locked tasks and then move one of them while locked. I take the other one and unlock it to push after the task dependency and it will move as intended. However, when you reapply the lock button it pushes the task back, for some unknown reason.
The functionality has been enhanced in Orchestrate version 7.75 where dragging tasks should not break maximum offsets; Fixed Offsets Only. Please upgrade to this version or above.
User experience has been improved when trying to drag tasks that are having same Min/Max offsets dependencies. This could massively mitigate the chance of breaking max offset.
For example, a Batch_104, op step 50 has Finish-Start relationship with op step 60 with a 0 Min and 0 Max Offset. When dragging op step 60, the planning logic is now aware and detects op step 50 and drags them together. The planning logic is now aware when dragging a task that has a 0 min and max offset with its predecessor.