Milestones
Key dates & importing them
Key dates are project markers — kickoff, a workshop, a launch, a conference — that aren't work to schedule. They render as labelled lines across every view so the team always sees what the plan is aiming at.
Key date vs task
A task has duration, an assignee, dependencies, progress. A key date is just a point (or a range) in time with a label — nothing schedules around it and it has no critical path. Use a key date for “this is fixed and external”; use a task for “this is work we do.”
A multi-day key date reads as one continuous bar across every day it covers, in Gantt, Calendar and Workload alike — overlaps are handled cleanly.
Bulk-importing key dates
In Manage Key Dates, open Import: paste a list or upload a .csv. A live preview shows exactly what will be created before you commit — what you see is what gets imported.
One key date per line, comma-separated:
- Format: label, date [, endDate] [, color] — e.g. Launch, 2026-06-01 or Conf, 2026-09-10, 2026-09-12, amber.
- Dates must be YYYY-MM-DD. Ambiguous forms (06-12-2026, slashes) are rejected rather than guessed.
- Wrap a label in quotes if it contains a comma: "Summit, Lisbon", 2026-11-02.
- A header row and blank lines are skipped; bad rows are reported, not silently dropped.
“I imported dates but don't see them on the chart.”
Check the Key dates toggle is on — with it off they neither render nor stretch the timeline. The chart also spans your key dates, so a date far outside the task range now pulls the timeline out to include it instead of sitting off-canvas.
Recap
- Is — a labelled marker, not schedulable work.
- Import — paste or .csv; live preview = exactly what's created.
- Format — label, YYYY-MM-DD [, endDate] [, color]; quote commas.