Expand my Community achievements bar.

Accepting commit dates

Avatar

Level 5

6/16/17

When a user commits to a new date on a task, the project owner should:

1. receive an email that clearly communicates they need to either accept AND/OR decline this new date (currently the project owner receives an email with a button titled 'See More Details', this doesn't make it clear that they have action to take)

2. have the ability to decline this new commit date, which would autoset the date of their task back to its original planned completion date

3. the commit date should populate into their approvals section so they have a running list of new commit dates awaiting their approval

3 Comments

Avatar

Level 5

6/16/17

The system also shouldn't require project owners to accept their own new commit dates. AND when a project owner clicks 'Does the effect project timeline', the gantt chart opens, which provides NO detailed information on how the timeline is actually impacted.

Avatar

Level 9

11/7/17

This would be really helpful! We have spent a lot of time researching why a project is projected as At Risk and it usually has to do with the commit date and the PM not knowing that the commit date is later than originally planned.

Avatar

Level 1

5/9/19

‚Agree - Major issues with commit dates - especially when a user doesn't realize that they are actually changing an end date to a task that can actually impact or push out the end date of a project. Users should not be able to change due dates of any kind without approval from the PM. We have the same types of issues with At Risk status and a PM not knowing why or even being able to change it. Right now only the user can change the commit dates - not even a system admn can change them without having to log in as the user. Additionally we have had issues with commit dates actually changing the due dates to where the work is due before it is even planned to begin.