Commit Dates are killing us

[DavidCo3]

Hi, Commit Dates are really killing us and causing a lot of confusion/frustration with users. e.g. A task is originally scheduled for a certain date and an assigned user clicks 'Work On It', Workfront sets the commit date to the planned date (assuming the user doesn't propose an alternative commit date - and we ask them not to do this). If the task's planned date is later changed, the user's original commit date remains. Our users don't remember to go and update their commit dates on such tasks. This then affects tasks' and projects' projected dates, and more confusingly for the user, it leaves the original commit date on their mini-calendar on the My Work screen. We would love to just be able to switch off the Commit Date functionality completely. As this doesn't appear to be possible, how else can we try to keep the commit dates aligned with the planned dates? There doesn't seem to be a way to centrally edit commit dates (even one-by-one, let alone in bulk). The only way I know of doing this is to log on as the user and change the commit date on each task. This is impractical with thousands of tasks in progress per month. Do other customers have this issue? How do you handle it? We have a team who are in charge of scheduling people at the right time, so we really don't need the users to be setting alternative commit dates. Thanks, David.

[Mohini__Mini_Si]

I agree with everyone here. Get rid of them completely.

[Former Community Member]

Removing them already! In Reply to Mohini (Mini) Sinha:

I agree with everyone here. Get rid of them completely.

[VicAl]

Is your timeline (dependancies plus duration) driven by the Planned Completion Date or the Projected Completion Date? Ours is driven by the Planned Completion Date and thus the Commit Date doesn't change the timeline.

[Former Community Member]

We use planned completion date and the commit dates don't interfere with the baseline or overall timeline. However it's confusing to our team and causes them more work by having to accept any date changes to the project or their tasks will still have the original commit date and not get updated. It's more trouble than it's worth just to get the team members buy-in or agreement for doing the assignment as I understand it was design for. In our enviroment we gain the buy-in and their work estimates through our planning activities so they are fully aware of when we need them to perform work.

[VicAl]

Yeah I have a Dashboard that lists the Tasks Completed Last Week and the Tasks Scheduled for this week and we review those in our Weekly Status Meeting so everyone knows what they’re working on. The only time I pay attention to the Commit Date is if someone changes it. As the PM I get notified and if the new date is ok, I change the Planned Completion Date. If the new date is not ok, I at least know to have a conversation and go from there. Vic Alejandro, PMP, CSM | IT | Project Manager IV Denver Water | t: (303-628-7262) | c: (303-319-6473) http://www.denverwater.orghttp://www.denverwater.org INTEGRITY | VISION | PASSION | EXCELLENCE | RESPECT

[Doug_Den_Hoed__AtAppStore]

Hi Non Commiters, I have an update on this that covers the Good, the Bad, and the Ugly. Let's go backwards. The Ugly: I confirmed with Workfront that there are no plans to change how the Commit Date behaves in the near to mid term. The Bad: once a User chooses Work On It, the Commit Date cannot be cleared, even by the API The Good: as mentioned, I am pleased to announce that (by popular demand on this thread) AtAppStore has developed a Syncronize Commit Date plugin for our UberCalc AtApp. Every hour (and on ad-hoc button click) it will automatically search for EVERY incomplete editable Tasks whose Commit Date differs from its Planned Completion Date and FORCE the Commit Date to match the Planned Completion Date. In doing so: Planned Dates Trump Commit Dates Assignees need not "remember" The My Work Calendar dates match Plan We intend to release the Synchronize Commit Dates plugin next week. Long term, it will have a one time installation fee of its own, but in appreciation to those on this thread who helped us (ahem) commit to this enhancement, will waive it for any customer who licenses UberCalc before August 31, 2016. Thank you for raising the interesting Challenge! Regards, Doug

[VicAl]

But the Commit Date should not be effecting your timeline. The timeline uses your Planned Completion Date (which is unrelated to and not connected to the Commit Date). So I guess I’m not understanding why the Commit Date would mess up anyone’s plan. Am I missing something? Vic Alejandro, PMP, CSM | IT | Project Manager IV Denver Water | t: (303-628-7262) | c: (303-319-6473) http://www.denverwater.orghttp://www.denverwater.org INTEGRITY | VISION | PASSION | EXCELLENCE | RESPECT

[PhilipSt]

Hi Vic, The problem we have is that once a User has changed the commit date, that's the date the User sees, not the Planned Date. So, there is the very real possibility of the PM expecting completion on one date, and the User working to a different timeline. Now, the PM can accept that new date (then it becomes the new Planned Date), but if your project is getting a lot of updates, it's easy to miss... Best to have the opportunity to disable the Commit Date at least .. Cheers, Phil

[EricLu2]

Hi: Commit Date functionality would be fine if it were not linked to Planned date in any way. Presenting it as the due date to users is what generates all the confusion for us. As far as we are concerned, the Planned Date is the date the deliverable is due. The commit date is not necessarily related, from a business perspective, to that planned date. I don’t like how WorkFront software has logic that relates, or changes behavior, based on that Commit date. Good explanation, Phil. It really brings into specific relief the reason why we don’t like the Commit Dates. Thanks! Eric

[MichaelLa1]

Thanks, Doug! This sounds like a great workaround and something that would work for us in the short term. I'm not familiar with UberCalc currently. Will definitely check back next week.

[VicAl]

Ah, gotcha. Thanks. Assuming they're not changing that soon. Would it be possible to create a report or filter to list the Tasks where the Planned Completion Date and Commit Date are different. Might make them easier to spot and know to have a conversation. Vic Alejandro, PMP, CSM IT | Project Manager IV Denver Water | 303-628-7262 Sent from my fancy phone -------- Original message --------

[EricLu2]

I can tell you what doesn't work :) I create a task report, then put in this text mode filter: numberOfChildren=0 numberOfChildren_Mod=eq plannedCompletionDate=commitDate plannedCompletionDate_Mod=ne That throws an error that leads me to believe this isn't how it should be done. Anyone got a better idea? Thanks, Eric

[PhilipSt]

Vic,

Yes, I do not have a report, but I do have a Project Task view set up. Yes, it is very useful!

See Attached

Cheers,

Phil

[Doug_Den_Hoed__AtAppStore]

Hi Eric, Try the advanced FIELD: argument in your filter: numberOfChildren=0 numberOfChildren_Mod=eq plannedCompletionDate=FIELD:commitDate plannedCompletionDate_Mod=ne Also, scrolling up to my previous post, I'd like to confim that our Synchronize Commit Date solution (overriding it with Planned Completion Date) would match the culture at your organization: conceptually, you believe that making that override global (vs allowing certain people or tasks to opt out) would be best? Regards, Doug

[EricLu2]

<> Well done. That works delightfully. Thanks! Eric

[MichaelLa1]

Doug - re: " conceptually, you believe that making that override global (vs allowing certain people or tasks to opt out) would be best?" Yes, most definitely. Commit dates don't mean a thing to us as we strictly use Planned Completion to manage our projects. Obviously, can't speak for everyone.

Re: commit date report - we use a modified Working On tab view so that the Planned Completion Date shows up next to the Commit Date. It removes the need for yet another report and it's an easy way for the user to spot the differences. They can also click on the commit date and make the update right in the Working On tab (see screen grab enclosed). It's still not ideal because it is a non-value added step for us. Doug's new UberCalc will automate that step for us (my group will buy me breakfast, lunch and dinner for the next 3 months if it works the way Doug says it will).

[LauraRa1]

Hi everyone I've been following this post for a while and I may have missed something so forgive me if this has already been pointed out..... You can hide the 'commit date' from the task assignee. We have removed it from view for everyone and we have replaced it with 'Planned date' in the individual task view of 'my work' page. Now they always work to the 'planned date'.

[Doug_Den_Hoed__AtAppStore]

Laura, you're correct: hiding the Commit Date is certainly an option. However, Workfront will still always automatically fill it in when the person accepts the work (e.g. whether you're using My Work, or the "Work on it" button, etc.), defaulting it to the Planned Completion Date at that time . And that is where the snag is: should the Planned Completion Date be revised later, other dates that are built in to Workfront's UI will still show the now out of date Commit Date. As Phil and others have suggested, out of the box, you can then create some exception reports to help highlight the differences, but the onus is still on the end user to note the difference and update the Commit Date to make it match, which seems inefficient to many people. Michael, I could not asked for a more affirming testimonial than yours that we're on the right track with our Synchronize Commit Date plugin. At the risk of aiding and abetting your team's intention to clog your arteries with 3 meals day, thank you! We're on it, and I'll announce on this thread when it is released next week. Regards, Doug

[LauraRa1]

Ah, ok, now I see the issue. Thanks for clarifying Doug. Laura Ray Project Support Analyst Bakkavor Information Systems Bakkavor Group West Marsh Road, Spalding, Lincolnshire, PE11 2BB, UK Direct: +44 (0)1775 763 010 www.Bakkavor.com // Laura.Ray@Bakkavor.com< [cid:image001.png@01D1E3F1.A9677C10]

[Doug_Den_Hoed__AtAppStore]

Hi folks, As promised above, AtAppStore is pleased announce that our Synchronize Commit Date solution is now available and included with our UberCalc AtApp until August 31, 2016, which (to recap) will automatically search for EVERY incomplete editable Tasks whose Commit Date differs from its Planned Completion Date and FORCE the Commit Date to match the Planned Completion Date, so that in turn: Planned Dates Trump Commit Dates Assignees need not "remember" The My Work Calendar dates match Plan Regards, Doug

[KarenRu]

Doug- We still have launched yet- new "go live" date is Sept 1st! I'm going to forward this threat to our implementation consultant- to make sure I fully understand the commit date issue- and based on what I've read here- I think it will annoy us too- so will like to see how the new solution you offered works! I'll reach out offline- thanks! Karen