Timeline

The Timeline tab is the project's schedule view. It lays out every dated milestone, epic and task as a bar across the project's date range, and adds four pieces of schedule intelligence: a baseline you can freeze and compare against, the critical path through your task dependencies, a burndown / burnup for the active sprint (or the whole project), and a one-line status report.

Use Timeline when you need to answer "Are we on schedule, what is holding us up, and how much is left?" — in a weekly review, before a client update, or when the plan is re-agreed. Project managers maintain it; members and viewers use it to see where their work sits.

Timeline reads the same planning data as the Planning tab. Milestones, epics and sprints are created and run on Planning; Timeline adds quick Milestone and Sprint buttons and the Capture baseline action.

Where to find it


Sidebar	Project section (under the project picker) → Timeline
URL	`/projects/{project}/timeline`, for example `/projects/42/timeline`
Command palette	Type Timeline — Timeline · {project name} under Current project

Who sees it:

The Timeline tab is shown on every project, to everyone who can open the project, on every plan including Free.
Capturing a baseline and creating milestones need edit rights on the project (see Permissions). Creating sprints also needs the Standard plan or higher.

Screen tour

Header card

Element	What it shows
Title	Timeline — Planning center: milestones, scheduled work, and sprint cadence in one view.
Buttons (top-right)	Milestone and Sprint.
Stat strip	Milestones (completed/total), Epics (completed/total), Sprints (total), Timeline rows (number of rows in the schedule), Active sprint (name or None).
Range chip	Range {start} to {end} — the schedule window. It runs from the first day of the month of the earliest date in the plan to the last day of the month of the latest date. With no dates at all it covers this month and next.
Risk chips	Overdue, Blocked, Unassigned, Unscheduled task counts (amber when above zero). Same definitions as on Planning.

If loading fails you see "We couldn't load the timeline." with Retry.

Timeline intelligence card

Title Timeline intelligence — Baseline, critical path, burndown and project status from the current schedule. Capture baseline is at the top-right.

Box	Main line	Detail line
Baseline	Captured {date} for the most recent baseline, or No baseline captured.	{rows} rows · {open} open tasks · {overdue} overdue — the current schedule's figures, so you can compare them with the baseline you agreed.
Critical path	{n} tasks · {n} dependencies — the length of the longest dependency chain and the total number of dependency links in the project.	The first four tasks of the chain by key, e.g. ALN-4 → ALN-9 → ALN-14 → ALN-17, or No dependency chain yet.
Burndown / burnup	{total} {points or tasks} · {Active Sprint or Project}.	{start} to {end} · {n} remaining, then a small chart.
Status report	{n}% complete · {project status}.	{n} blocked · {n} timeline rows.

How each figure is worked out:

Figure	Rule
Critical path	The longest chain of tasks connected by dependencies (counted in tasks, not days). Dependencies are the links you add in a task's Dependencies section (Blocked by, Blocks, Related to, Duplicates).
Burndown scope	The active sprint's tasks when a sprint is active; otherwise all project tasks.
Burndown unit	Points when the scope's tasks have story-point estimates; otherwise a count of tasks.
Burndown period	The active sprint's start and end dates. With no active sprint, from the earliest to the latest task date (start, due or completed). The chart covers at most 30 days.
Remaining / completed	For each day, completed is the work of tasks marked Done by that day; remaining is total minus completed. The chart draws remaining (falling line) and completed (rising line).
% complete	Done tasks ÷ all tasks in the project, rounded.
Project status	The project's status from its Settings.

When there is nothing to chart the box shows No burndown data yet.

Schedule card

Title Schedule — Dated milestones, epics, and tasks. Unscheduled rows stay visible. A badge shows {n} rows.

Rows are listed milestones first, then epics, then tasks (tasks by due date). Each row has:

Column	Meaning
Name	Milestone, epic or task name.
Detail	Type (Milestone, Epic, Task) · status · owner (the task's assignee).
Bar	Position and length inside the range. Every scheduled bar is drawn at least a little wide so one-day items stay visible.
Unscheduled	Replaces the bar when the row has no end date (milestone due date, epic target date or task due date).
Dates	{start} to {end}. (inferred) after the start means the item had no start date, so the bar starts one week before the end.
Progress badge	Tasks: the task's progress %. Milestones and epics: share of their tasks that are Done.
Blocked	The task is marked as blocked.
Overdue	The end date has passed and the row is not Done, Completed or Cancelled.

Done and cancelled tasks stay on the schedule so you can see what was delivered.

Empty state (no milestones, epics or tasks yet): Add a milestone to begin your roadmap — Milestones, epics, tasks, and sprints will populate the schedule.

Milestones and Sprints cards

At the bottom, side by side:

Card	Content	Empty text
Milestones — Roadmap moments by due date.	Each milestone: name, Status · Due {date}, progress % and bar.	No milestones yet.
Sprints — Recent cycles and velocity.	Up to four sprints (active, planned, then completed): name, dates, status badge and {done}/{planned} tasks · {done}/{planned} pts · velocity {n}.	No sprints yet.

These cards are read-only. To edit, complete or start items, use Planning.

Tasks

Capture a baseline

A baseline freezes today's schedule figures so you can later see how far the plan has moved.

Open Timeline.
Click Capture baseline (top-right of Timeline intelligence). There is no confirmation step.
You see Timeline baseline captured. The Baseline box shows Captured {today}.

What is stored with each baseline: the schedule range, number of rows (scheduled and unscheduled), total, open, completed, overdue and blocked tasks, and the open estimate in minutes and points. Each capture adds a new baseline; the box always shows the latest one, and the capture is recorded in the project's Activity (Timeline baseline captured).

If it fails you see "Could not capture the baseline."

Create a milestone from Timeline

Click Milestone (top-right of the header).

Fill in New milestone:

Field	Required	Rules / defaults	Notes
Name	Yes	Up to 160 characters.
Status	No	Choose Planned (default), Active or Completed.	The list used to offer In progress, which the server rejected with "The selected status is invalid."; since 5 October 2026 it offers Active, the same as Planning.
Start date	No	A date.
Due date	No	On or after the start date.	Without a due date the milestone appears as Unscheduled.

Click Create. You see Milestone created. The milestone gets a row in the schedule and a card under Milestones.

Create a sprint from Timeline

Click Sprint.

Fill in New sprint:

Field	Required	Rules / defaults	Notes
Name	Yes	Up to 160 characters.
Status	No	Planned (default), Active, Completed.	Prefer Planned and use Start on Planning, which enforces one active sprint.
Start date	Yes	A date.
End date	Yes	On or after the start date.

Click Create. You see Sprint created.

This quick dialog has no Goal or capacity fields. Add them afterwards with Edit on the Planning tab.

Read the schedule

Look at the Range chip to see the window the bars cover.
Scan for Overdue and Blocked badges.
Check rows marked Unscheduled or (inferred) — give those items proper dates on the task or in Planning.
Compare Baseline Captured … with today's detail line: more overdue or open tasks than when you captured means the plan has slipped.

Shorten the critical path

Read the first tasks in Critical path.
Open each one from Tasks and check its Dependencies.
Remove links that are not real, split long tasks, or run work in parallel. The path recalculates as soon as you reload Timeline.

What updates the timeline

You change…	Timeline shows…
A task's start or due date	Its bar moves; the range may widen to new months.
A task's status to Done	Progress badges, milestone/epic %, burndown and % complete update.
A task's assignee	The owner in the row detail; Unassigned chip count.
A dependency	Critical path recalculates.
A sprint Start / Complete on Planning	Burndown switches between Active Sprint and Project scope.
The project status in Settings	The status in Status report.

The tab reloads its data when you open it or after an action; it does not refresh live while you watch. Navigate away and back, or use your browser's reload, to see others' changes.

Statuses

Row statuses come from the item itself:

Row type	Statuses
Milestone, Epic	Planned, Active, Completed, Cancelled
Task	The task's workflow status (Backlog, Todo, In Progress, Review, Done, Cancelled, or a custom status your project uses)

Badges added by Timeline: Unscheduled, (inferred), Overdue, Blocked.

Permissions

Role	View	Capture baseline	Create milestone	Create sprint
Organization owner	Yes	Yes	Yes	Yes (Standard+)
Projects Administrator	Yes	Yes	Yes	Yes (Standard+)
Projects Manager who is a project Manager here	Yes	Yes	Yes	Yes (Standard+)
Projects Member / other project members	Yes	No	No	No
Project Viewer / guest	Yes (read-only)	No	No	No

The Milestone, Sprint and Capture baseline buttons are shown only to people who may edit the project (since 5 October 2026; before that they were shown to everyone and refused on save). On the Free plan, Sprint fails with "Could not create the sprint." Capturing a baseline and creating milestones work on every plan.

Worked examples

Example 1 — Weekly schedule check (everyday)

Every Monday Sara Khan opens Timeline for Al Noor Showroom Fit-out (ALN-FIT).

Header: Timeline rows 27, Active sprint Sprint 2, chips Overdue 2, Blocked 1, Unassigned 0, Unscheduled 3.
In Schedule she sees ALN-15 Ceiling approval with Overdue and Blocked, and three tasks marked Unscheduled.
She opens the three tasks and sets due dates; after reload Unscheduled is 0 and the bars appear inside the Range Nov 1 to Dec 31 window.

Example 2 — Baseline, slip and recovery (full scenario)

Omar Haddad agrees the plan with Al Noor Trading LLC on 2 November 2026.

Date	What Omar does	What Timeline shows
2 Nov	Clicks Capture baseline.	Timeline baseline captured. Baseline Captured Nov 2; detail 27 rows · 22 open tasks · 0 overdue.
2 Nov	Starts Sprint 1 on Planning (34 points).	Burndown 34 points · Active Sprint, Nov 2 to Nov 13 · 34 remaining.
9 Nov	—	Burndown … · 16 remaining; chart shows 18 points completed.
20 Nov	Weekly review.	Baseline still Captured Nov 2, but detail now 29 rows · 15 open tasks · 3 overdue. Critical path 6 tasks · 9 dependencies: ALN-4 → ALN-9 → ALN-15 → ALN-19.
20 Nov	Opens ALN-15 Ceiling approval (blocked, overdue), chases the client, removes a wrong Blocks link from ALN-19.	After reload: critical path 4 tasks · 8 dependencies; Blocked 0.
21 Nov	Agrees a new handover date (18 Dec) with the client, edits Handover on Planning, then clicks Capture baseline again.	Baseline Captured Nov 21; the Handover bar extends; range now ends Dec 31.
15 Dec	—	Status report 93% complete · Active, 0 blocked · 29 timeline rows.

The project Activity tab shows both Timeline baseline captured entries, so the date of each re-agreed plan is on record.

How it connects

Where	Link
Planning	Source of milestones, epics and sprints; start/complete sprints there.
Tasks	Task dates, status, assignee, progress, estimates and dependencies drive rows, burndown and critical path.
Calendar	The same dated tasks, by month and per person.
Settings	Project status shown in Status report.
Reports	Project status and delivery reports use the same task data.
Activity	Baseline captures and planning changes are logged.

Tips and common problems

Problem	Cause	Fix
"The selected status is invalid." when creating a milestone here.	You are on an old cached copy that still lists In progress, which is not a milestone status.	Reload the page and choose Planned, Active or Completed.
A task shows Unscheduled.	It has no due date.	Give it a due date in the task drawer.
A bar starts one week before its end with (inferred).	The item has a due date but no start date.	Add a start date for an accurate bar.
No dependency chain yet.	No task has a dependency.	Add Blocked by / Blocks links in task drawers.
Burndown says tasks instead of points.	No task in scope has a story-point estimate.	Add point estimates to tasks.
Burndown covers the whole project.	No sprint is Active.	Start a sprint on Planning.
Burndown chart stops after 30 days.	The chart is capped at 30 days.	Use sprints of 30 days or less for a full chart.
Baseline box figures don't match the baseline.	The detail line shows today's figures, not the stored ones.	Compare them with what you noted when you captured.
Two sprints became active.	A sprint was created here with Status = Active while another was running.	Set one back to Planned on Planning; create sprints as Planned.
Capture baseline refused.	You lack edit rights on the project.	Ask a project Manager or administrator.