In our environment, tasks come into our production queue project with due dates already set from a preceding step. I would like to automate setting the start date when someone is assigned to the task, so that workload reports correctly.
I see that we’re able to use rules to set the start date as a part of setting the due date as of December 2024, but there’s a flaw in the logic. Under current conditions, it’s not possible use a rule to set a start date without also changing the due date. Without a specified change to the due date, the action remains incomplete/unspecified and the rule cannot be saved. Our due dates are task-specific and cannot be set based on relative dates. It would be very helpful if we could set the start date without being required to set the due date, or if the due date had a “keep existing value” option.