WorldServer - Step Due Date cannot be changed for a specific step if the Due Date of another step is set to the past

The scenario is as follows:

A project is created with a workflow containing more than one human step, for instance, Translate and Review. The project manager sets specific step due Dates for the Tasks, for instance

Translate: September 3, 2024

Review: September 4, 2024

On September 4 2024, the project manager decides to change the Due Date for the Review step to September 5th, 2024. This change cannot be done or saved unless the past due date of the Translate step is changed to a future date, or removed in total.

It should be possible to change step due dates regardless of whether some of the due dates are in the past. Past due dates should be tolerated.

When changing the Step Due Date, you cannot set or leave a Due Date that is set in the past, no matter which step. The workaround would be to remove the past due date for the affected step (for instance Translate) and set the desired due date for the other step (for instance Review). Or just set the past due date of the Translate step to the future.

We have created an enhancement request for this: CRQ-39613. This article will be updated when and if a disposition for this change will be set.

Relevant article:

What is the difference between the Task Due Date and the Step Due Date columns and how to set them?
Starting from WorldServer 11.3., changing a Task's Due Date for one or more steps triggers an Email Notification related to Task Step Due Date Changed to all Assignees