Propose and Accept a Task Due Date on the Task List Page

When a task is part of a hand-off chain, directly modifying its due date may affect the due dates of other tasks in the chain. If the hand-off chain contains tasks from different companies, each company should be aware of the potential changes to their tasks. To solve this issue, updated due dates can be proposed without affecting the actual task due date. This enables the companies with tasks in the chain to review proposed due dates before they are accepted.

When a proposed due date is accepted, it is removed from the task and becomes the current task due date. If the accepted due date occurs on a non-work day, the Use Only Work Days setting is cleared and the due date is updated. If a task with a proposed due date is committed, the proposed due date is removed, and the current due date is updated to match the committed due date.

To learn more about task due dates, see Understanding Tasks App Concepts.

To propose and accept a task due date on the Task List page:

1. In the object selector, select ﱆ Project or  Program, and then select a project or a program from the list.
2. From the  Main Menu, select  Tasks, and then select Task List.
3. On the Task List page, select a task.
4. In the Proposed Due Date column, select a proposed due date for the task.
5. When you are ready to accept the proposed due date, right-click the task or select the  Context menu, and then select Accept Proposed Due Date.
6. All changes made to this page are saved automatically.

Tips

• The  Proposed Due Date icon in the State column indicates that the task has a proposed due date that has not been accepted.
• You cannot propose a due date on completed tasks.
• If a task is part of a hand-off chain, changing its due date directly, accepting a proposed due date, or setting a new committed due date will cause the task and other tasks in the chain to be moved. The current hand-off mode determines the movement of a hand-off chain when any of the tasks in the chain are modified:
  •  Keep Hand-offs: Maintain hand-off logic, but allow for the addition or consumption of slack between tasks.
  •  Break Hand-offs: Only maintain hand-off logic until the slack between two tasks reaches zero.