Automatically update Commit Date when the Due Date Changes

agree. if the date changes the user has to manually adjust their commit dates

I cannot vote "Yes" on this enough times to reflect the folks on my team requesting this ability.

Yes please. If the project task were to change (moving up or back) this change should feed to the My Work tab and change there as well. My team gets an update from me on each project that tells them they can flip flop the tasks to get the right dates. But there may be several tasks to flip back to "request to work on it tab" and then flop it back to "working on it" tab. What a waste of my time as well as theirs no matter if the change the dates on the actual My Work task or if the flip flop it.

My vote is Heck yes!

Even better - have a button/alert in the work item that tells a user that the Due Date has changed and that they should consider changing their Commit Date.

Take it one step further - add info on what the Due Date is, alongside the Commit Date - that way, users can see the clear distinction that their Commit Date is independent of the Task's Due Date in the Project.

I vote for the button/alert in the task item on the My Work page that Greg has proposed. (The user may not be able to commit to the new planned date - but they need alerted to make that change.)

Great idea, I keep having to explain this to our users...

or just get rid of the commit date all together? It is confusing for all of our workers and the fact that this date is much more front and center than the planned completion date - it's becoming harder and harder to ignore as a system administrator. I know a lot of people on the community site also agree that the commit dates get in the way more than they serve a good purpose in WF.

For our team the commit date is important because we work outside of our division frequently and may not be aware of other work items the person has available. This is an indicator for the PM to either have a conversation or accept the commit date as a new planned completion date.

This is exactly what we need in my organization. The date confusion is such a big deal for my users. Stuff in their working on, on the task, and then what they see on the project level rarely lines up.

yes and red line it somehow so we know someone assigned to the task or request pushed the date out