I still feel like one of the issues here is customization of the task page UI. The commit date can be a valuable tool. I do see some users interacting with it effectively and others who just don't get it no matter how many times we try to walk them through it. The simple fact that when a user nav...

Agreed. Being able to further customize to completely hide the commit date in the system would be extremely beneficial. I love the fact that the new calendar will go off the Planned Completion date and I've already customized the My Work page to remove the commit date from prominence but the fact t...

Sure thing. The first user to accept the task by clicking "work on it" sets the commit date. The system automatically defaults the commit date to match the initial planned completion date when the first user accepts the work. Changing the commit date after this requires an assigned resource to man...

Any of them. The commit date can be changed by any resource assigned to a task. Which brings up the question who owns it in collaborative assignments. Fun stuff, right? Change takes time, patience and practice.

Hi Laura, I think the overarching problem here is that changing this in the My Work page is not necessarily the end of the story. It obviously depends on how you're set up and how you're using the system but that commit date is front and center when you navigate in to any task page. The commit date ...

Agree with many of the posts on here about this topic. We also experience issues with commit dates. It's a nice idea from the perspective of giving your users a tool to set a new due date when they can't commit to the current planned date. BUT in practice it's a mess because we deal with shifting ti...