[Status: Not planned] Task Due Date History
We have an issue where at times people will change their due dates on the task itself and not give an explanation as to why. We can obviously see when the task had changed to the "new" due date, but at times we need to see what was put in originally.
Can this be made a feature? The history, the timeline of task due dates.
In addition to having visibility into due dates that have changed, we should also have the ability to lock due dates to prevent them from moving for certain tasks. When deadlines are missed, users can essentially hide their by simply pushing out the due date and BOOM they're not overdue anymore. There are many scenarios where we need accountability for hitting due dates but because date editing is not restricted, users are able to adjust their plans and that information is lost.
Hi Lisa,
We use mile stones for this purpose. Once the mile stone is set it can not be moved so even if someone moves their task date the milestone stays the same.
Thanks Adam! What prevents them from moving their milestones?
If i am correct if they arnt an admin of the project then they should only be able to change the tasks they are assigned to. So if you dont assign them to the milestone take then only you can change it.
Or you could change your user rights within a project to limited. That would take away the ability for them to change dates anyway. depends how much control you want your users to have really.
I think you're on the right train here - I think I just need more control over exactly what tasks can be completed. The 4 access roles Wrike has pre-built do not have the configuration of permissions I really need.
Hey everyone, thanks for all of your feedback here. Once this thread reaches 60 upvotes, our Product team will provide this thread with a status. You can read more about our process here. If you have any other questions, let me know 😊
Our team would very much like to see an Original Due Date field. We could use it to create a custom calculated field to see how long a task has been pushed back.
For example, let's say the task's Original Due Date was January 3, 2021. It is still active and now due on June 24, 2021, meaning the task has been pushed back 174 days.
This task is obviously stretching on and on forever and we need to reassess it. Maybe it needs more granular sub-tasks, or maybe we need to table it for now. Should we have a meeting to regroup? Why is this person pushing back the task so much? What's stopping it from being completed?
Hi Anna Wallace, thanks for sharing your thoughts and supporting this idea. I understand how this functionality can help your team. Please be sure to upvote the original post if you haven't yet 🙋🏻♀️
Thank you Anna - the scenario you describe is exactly the issue I'm trying to solve! Has anyone discovered a work around for this? I was thinking a custom field might work?
Welcome to the Community Geoff Luczycki 👋 A custom field can be a solution here and you can also track the custom field history 👍
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
We actually added a custom field for this on one of our projects. Since we added after the fact it was a manual process of adding in the original due date in the field, however, if it is done from the beginning I can see how that may be an easy solution.
I went ahead and added the final upvote to hit 60 since I would like to see this as a permanent field option.
Very bad that this feature is not on the short term as it gives essential possibility to track project progress.
An idea for all what we are doing as workaround:
we have a server in the background doing automated things. This server goes through all task regularly. For this case it is copying the due date to a custom field named "Original Date Due " if the custom field is not filled yet. So the original due date is saved (ok it does not prevent users from cheating, but that should be some kind of good practice that they do not change this field).
Furthermore we copy the start date to another custom field "start date auto" and the due date to a custom field "due date auto". This is done everytime the custom field is differing from the dates in the task. The advantage of custom fields: they have a history. So you get the history for start and due date.
I'm sorry about this disappointing news Sven Passinger. Thank you so much for posting your workaround here and as a separate post, that's super helpful! 🤗
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover