Skip to main content
New Participant
April 26, 2017
Archived

Automatically update Commit Date when the Due Date Changes

  • April 26, 2017
  • 16 replies
  • 2189 views

The majority of our team sorts their My Work area by Commit Date but when a task due date changes, the commit date stays the same. It would be great if the commit date would change to re-prioritize on the user's Working On tab.

16 replies

New Participant
November 25, 2018

Hi Shawna,

I totally agree....this topic has already been voted on in another thread beyond the 45 votes required and WF said they had no plans to change it. I've been active in the community for the last 3 years or so, and this issue has a lot of support for change....keep pushing and hopefully they will listen and provide customers with the ability to completely deactivate the Commit Date functionality if they wish to.

On the topic of your concerns with the new Home screen, are you saying that you have PMs with admin level access who login as other users in order to check which task commit dates don't match planned dates? As a much easier alternative you can write a task report and add the following text mode to the filter:

plannedCompletionDate=FIELD:commitDate
plannedCompletionDate_Mod=ne

At least this will let you work out which users have tasks which don't match and you can then ask them to correct their Commit Dates.

Still a massive waste of everyone's time, and hopefully Workfront give us a proper solution.

Regards, David

New Participant
November 14, 2018

Automated would be great! We definitely need a solution to this!

New Participant
November 14, 2018

This has been an issue for years. we have seen this same subject come up in workfront Leap sessions over and over with no solutions. now with the new home view we do not even have an opportunity to use our work around (which we have had to use for the past 4+ years.

before we were able to have a custom layout template that had both planned and commit dates showing. we had a PM go in regularly and "match dates". this was already time consuming, but with the new roll out of home page view it would take us DAYS to check everyone's my work and see if there were unmatched dates. calendars are effected by this and people will miss deadlines. we need a solution.

We are all very concerned about the roll out in January.

New Participant
November 14, 2018

Totally agree with this!!

Idea: Have the ability to NOT use commit dates in set up. Commit dates cause problems for our team, especially in the new HOME area where we aren't able to see planned vs commit dates and adjust accordingly as workers. It wreaks havoc on our calendars as dates don't match when Project Managers change dates and Workers don't match them.

New Participant
July 10, 2018

Yes % without a doubt this should be automated! Its time consuming and the commit date makes it more confusing, It doesn't seem to make sense why this would not be automated? This NEEDS to be changed!

Thanks , Steve

New Participant
July 10, 2018

This is a must have for our company... we are always rearranging dates and it requires everyone on the project to adjust their dates. This takes extra time that we could use doing actual work. I was actually blown away when the customer service rep told me that this didn't already work in this manner.

PLEASE MAKE THIS CHANGE!!!

Thank you

New Participant
December 4, 2017

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

New Participant
November 3, 2017

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.

New Participant
September 21, 2017

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.

New Participant
September 21, 2017

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.