Commit Dates are killing us | Community
Skip to main content
D
DavidCo3
June 29, 2016
Question

Commit Dates are killing us

  • June 29, 2016
  • 75 replies
  • 8014 views
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.
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

75 replies

Show previous replies
E
EricLu2
October 26, 2016
Oh yes, I can help. The problem has to do with the fact that the commit date does not have a time associated with it and the planned date does. Adjust your report to show the hours associated with each attribute and you’ll see what I mean. When you compare the two, even though the date is the same, the hours are different, so they do not match. The next thing you’ll do is try to use the CLEARTIME function to truncate the hours from the task. Um, CLEARTIME doesn’t work correctly. I’ve had a ticket open for months trying to get them to fix it. We still don’t know how to compare those dates in a way that gets around the hours, using the functionality WorkFront currently provides. ☺
L
LauraRa1
October 27, 2016
Ok, I’m not completely sure why I would want to truncate the hours. I believe you for sure but I want to understand what you’re suggesting. So the report I’ve produced where I have a column in days of the difference between the two dates isn’t accurate then either? I think I’m ok with that because at least it puts up a red flag. Wondering what I’m missing. Thanks Eric ☺ 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:image002.png@01D2302C.19F5D040]
E
EricLu2
October 27, 2016
Hi: Here is an example: Planned Completion Date: 15-DEC-2016 10:30:00 Commit Date: 15-DEC-2016 00:00:00 When you compare them, they aren’t the same, because the times are different. The CLEARTIME function is supposed to zero out the hours, so that CLEARTIME(“15-DEC-2016 10:30:00”) will yield “15-DEC-2016 00:00:00”. I tried to create a custom attribute (Commit Variance) where it is equal to DIFF(CLEARTIME(Planned Completion Date), Commit Date) (I know that isn’t the exact syntax, but you get the idea) That doesn’t work because the CLEARTIME function is not working right. Does that help? Eric
L
LauraRa1
October 27, 2016
Got it, makes sense now. I hadn’t come across the CLEARTIME function yet so I’ll not worry about it until they get it working. Thanks Eric ☺ 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@01D2304D.1D231860]
E
EmilyHi
March 9, 2017
Just a note that I have added this topic to the new idea exchange and would love to get some votes :) This is a very big pain for our creative department. I think our problem would be fixed if we had the option choose planned completion over commit dates on the My Work calendar strip and on the task page.
D
DavidCo3Author
March 9, 2017
Hi Emily, Which is the one that you raised? There is one in the Project section regarding commit dates: https://support.workfront.com/hc/en-us/community/posts/115001085547-Give-system-admins-an-option-to-remove-Commit-Dates-from-the-system- I've added my vote to this one, anyways! Cheers, David
E
EmilyHi
March 9, 2017
Shoot. I didn't realize that the same thread existed in another section. I added mine to the My Work section. Maybe we can vote on both and be twice as heard :) EMILY HIGINBOTHAM PROJECT MANAGER
J
JosephCa
March 10, 2017
Hi All - By using a Layout Template you can set the functionality for users to use Planned Completion Date, replacing Commit Date. Pretty easy edit under Setup -> Interface -> Layout Templates. If you don't have one already, you will need to create a new one to get this functionality. Join me on LinkedIN
D
DavidCo3Author
March 10, 2017
Hi Joe, Yes - that helps, but it doesn't remove the Commit date from the Task screen or mobile app. Regards, David
J
JosephCa
March 10, 2017

[image: Inline image 1] It will remove it from the "Banner, if set for "Working On" tasks, and/or "Work Requests". You may want to also remove it from any existing Task, Issue or Project View to further restrict users from accessing it - therefore using it. Not 100% on mobile - but I believe you still are set within your Access/Layout. Maybe not? On Thu, Mar 9, 2017 at 6:33 PM, David Cornwell < globalforum@communitylists.workfront.com> wrote: > Hi Joe, > > Yes - that helps, but it doesn't remove the Commit date from the Task > screen or mobile app. > > Regards, David > > -----End Original Message----- > -- Joe Catlett Consulting Services, PM jcatlett@leappoint.com 801-300-9526

Show more replies
Terms & ConditionsAccessibility statement

Loading footer...