Is there a setting or best practice way to create a “hard stop” date on a Task so that the Assignee cannot change the Due Date?
The easiest example is a live event on a set date, the date and time cannot change. We’re setting up Task dependencies and understand how to use both the Timeline and Task views for setting Start, End, and Dependencies, but haven’t determined how to set an “unchangeable” due dates for key tasks.
Can or has this been turned into a product update request yet? It feels like this would be a valuable feature. Workarounds just create additional work and need for monitoring. Thanks!
Hello there,
would it be sufficient to just have the mentioned rule in every original project instead of multi homing all of the tasks in every project to a “locked dates” project that has this rule?
Regards,
Boris
@Boris_Gemünd Yes if 1. you don’t care about the rule applying to all the tasks (you can’t pick and choose easily) 2. you don’t care about creating the same rule multiple times
@Phil_Seeman , I think it should be noted that the Last modified date is for anything modified on the task, not just the due date.
@Jennifer_Ann_Morelan , one way around this is to check the task details pane, at the bottom the All activity (audit log) which will show you when & who changed the due date, but unfortunately it won’t indicate what the previous due date was.
A more visual solution could be to use the Gantt view (click on the + at the end of your tabs along the top of your project, after Files) and in Options enable the Baseline feature which will visually show slippage of tasks.
You could also create a Date type field and use that for your ‘Original’ (or Baseline) date, while the native Due date field changes as the project progresses. And you could also add a formula field to display the difference. However, currently, you will not be able to lock the Baseline date field, yet.