I’m working with dynamic dates in Automation and am running into some unexpected behavior. I’m hoping someone else has tackled something similar.
Here’s the setup:
- Trigger: When task status changes to All Completed
- Action: Change due date to Today()
The due date portion is working exactly as expected.
The issue I’m seeing is with duration and start date behavior. When the automation updates the due date to Today(), the task’s original duration is preserved. Because of that, the start date rolls backward from today.
What I was expecting instead was for the start date to remain unchanged, since the task owner wouldn’t have realistically started the work earlier than the originally scheduled start date.
I’m trying to avoid start dates shifting earlier than originally planned when using dynamic due dates, and I’m wondering if there’s a way to:
- Lock or preserve the original start date, or
- Prevent duration from driving the start date backward when the due date is updated via automation
I feel like I may be overlooking a configuration option or a smarter automation pattern here. Has anyone implemented something similar or found a workaround?
Thanks in advance for any insight.