Understanding start dates, due dates and late items
This FAQ article explains how start dates, due dates work in GroupCamp and when tasks and milestones are considered late.
Due dates on tasks and milestones are due at 23h00 (11PM) in the time zone of the project
Late task due to start dates
If the percentage completion for a task with a start date is at 0% past that start date, the task is considered as being late since it has not yet started.
Late task due to due dates
When the due date of a task is past and the task is not completed that task is considered as being late.
Late task due to both start dates and due dates
This scenario combines the two previous cases:
Late task due to a past date on a milestones linked to a task list
In the example above, the task is due for the date which is set on the milestone linked to the task list. Since we are past that date, the task is considered as being late.
On the 3rd of May the second task is not considered as being late since it has its own due date.
Late task due to start date on a parallel task
When a task is assigned to multiple members and all of the members have not started their assignment (percentage completion equals 0%), the task is considered as being late.
Late task due to a due date on a parallel task
Even if all assignments on a parallel task are completed the task is still considered as being late if the head task is not completed. A task assigned to multple team members requires an additional validation at the head task level for the task to be considered as being completed.