Past due tasks

A task is considered past due if the task's status is neither Complete nor On Hold, and the due date has come and gone.

Note: when a task's due date is set, the due date is set as the end of the day in the timezone of the task creator. For example, say we have a task that was created on September 1, 2020, by a task creator in the timezone US-ET. The task's due date equals December 1, 2020. If after December 1, 2020, 23:59:59 US-ET (or 11:59:59 pm US-ET), the task's status is neither equal to Complete, nor On Hold, the task will become past due.

A task will be identified as past due in the below sections.

List

Within List, you can identify a task as past due if the due date is yellow.

Task Details drawer

Within Task Details drawer, you can identify a task as past due if the due date is yellow.

You can also identify any dependencies as past due if the due date is yellow.

Timeline

Within Timeline, you can identify a task as past due if the task is yellow.

Additionally, the dependency line connecting two tasks is yellow allowing the task with a dependency to quickly identify any dependent tasks as past due.

Reporting

Within Reporting, you can identify past due counts in all sub-reports.

Plan

Within the Plan sub-report, you can identify past due counts by hovering over the dates. 

Notes:

• if a task was due on 4-June, the task will display as past due beginning on 5-June. If the task status is not changed to Complete or On Hold, and the due date is not changed to the future date by 6-June (for the user who created the task), then the past due count will remain forever.
• if, however, by 6-June, the task's status is changed to Complete or On Hold, or the due date is changed to a future date, the past due count will be removed

Teams

Within the Teams sub-report, you can identify past due counts by hovering over where yellow.

My Work

Within My Work, you can identify a task as past due if the due date is yellow.