Maintain dates, dependencies and project progress

Investigate schedule contradictions and commitments that cannot be met.

Investigate schedule contradictions and commitments that cannot be met.

Review the timeline

Product location: /planner/{planId}/timeline (fallback: /planner)

Open the project Timeline and inspect its phases, work items, milestones, owners and dependencies. Check whether a date is calculated or pinned before changing it.

A critical milestone defines a commitment for critical-path analysis. If no milestone is marked critical, the overview has no critical commitment to work backwards from.

Recalculate and investigate

Product location: /planner/{planId}/timeline (fallback: /planner)

Use Recalculate schedule, then review the overview's diagnostics.

Diagnostic

Review action

Dependency cycle

Remove or correct a link in the loop; no schedule can satisfy circular dependencies.

Pinned-date conflict

Decide whether to move the fixed date or change the preceding work. The pinned date is retained.

Over-committed person

Review overlapping assignments and available capacity. The warning does not automatically move work.

Broken link

Reconnect the intended source record or remove the obsolete plan item.

Plan and work disagree

Compare the due date in the owning module with the plan's requirement.

Record progress in context

Product location: /planner/{planId}/board (fallback: /planner)

Use the Board for work status and open linked records when their completion needs to be recorded in another module. Inspect any manual progress override before interpreting a summary percentage.

Recalculate after meaningful date or dependency changes and check whether the affected milestones are now achievable. A calculation can expose a conflict; resolving it remains a planning decision.

Did this answer your question?
😞
😐
😁