Flow: timeline
The timeline is a Gantt chart view: a list of objects on the left, a scale of days on the right, and for each object a bar from its start date to its due date. It shows at a glance what runs in parallel, where tasks overlap and which blockers are holding work up. You change dates right on the scale by dragging a bar or its edges. The end of the article covers the same dragging in the calendar.
Where to find the timeline
The "Timeline" tab sits next to "Table", "Board" and "Calendar" for every type whose schema has a "Date" or "Date and time" field. If the type has no dates, the timeline suggests adding a field: "The type has no date fields. Add a “Date” or “Date and time” field in the type settings." — along with a "Type settings" button.
In new workspaces created from the "Tasks" template, tasks already have a shared "Timeline" view: start is "Start date", due date is "Deadline", scale is "Week", grouped by project, with blocker arrows.
How the screen is laid out
Above the scale are the type's common toolbar (views, search, "Filters", "Assignee") and the timeline settings:
Setting | What it does |
|---|---|
"Scale" | "Day", "Week" or "Month" |
"Start" | The date field where the bar starts; "—" means no start |
"Deadline" | The date field where the bar ends; "—" means no due date |
"Group by" | "No grouping", "Assignee", "Status" or a many-to-one relation field (for example, "Project") |
"Back", "Today", "Next" | Scroll the scale; "Today" returns to the current date |
By default the start is the "Start date" field (start_date) and the due date is the "Deadline" field (due_date); if there are no such fields, Flow uses the type's last date field as the due date. The same field can't be both the start and the due date. If you pick "—" for both, Flow asks you to "Choose a start or due date field."
Scale and zoom levels
Scale | Visible range | Units |
|---|---|---|
"Day" | 8 weeks | days, weekends highlighted, months on top |
"Week" | 26 weeks | weeks, months on top |
"Month" | 12 months | months, years on top |
Today is marked with a vertical line. The "Back" and "Next" arrows shift the scale by half a screen so that neighboring screens overlap. Within the window you can also scroll the scale without the arrows.
Rows and bars
On the left are the object name (a link to its card) and the assignee. On the right is the bar:
both start and due date set — a bar from start to due date inclusive, with the name on it;
only one date set — a dot on that day;
start later than the due date — a dot on the due date.
The bar color follows the object's status type (in progress, done and so on). Hover over a bar to see a tooltip with the name and dates. Clicking a bar opens the card.
Objects are sorted by start date. When grouped, each group has a header with the number of objects; clicking it collapses or expands the group. Objects without a value go into the "Unassigned", "No status" or "No “Project”" groups.
Objects without dates
Objects with neither a start nor a due date are collected below the scale in the "No dates" block. To set a date, drag the object with the mouse onto the day you want, or click the calendar icon — "Set to today". The object gets a due date (or a start date, if there is no due date field). Up to 100 objects without dates are shown; the rest appear as an "N more" line.
Changing dates
Dragging works with a mouse or a pen:
drag the whole bar — both the start and the due date move by the same number of days;
drag the left edge — only the start changes;
drag the right edge — only the due date changes;
stretch a dot — if both fields are selected for the type, the dot becomes a bar and the second field is filled in.
You can't drag one edge past the other. On the "Month" scale the bars are narrow, so they have no edges — you can only move the whole bar.
With the keyboard. Select a bar with Tab: the ← and → arrows move it by one day, Shift plus an arrow changes only the due date, and Enter opens the card.
How changes are saved. The bar moves to its new position immediately, and Flow saves the change to the object. For a "Date and time" field, the original time of day is kept. If saving fails (for example, you don't have permission to edit the object or the field), an error appears and the bar snaps back. If someone else changed the object in the meantime, Flow shows an error and reloads the timeline.
Rescheduling is recorded in the object's history like any field edit, and it triggers automations and reminders in the same way.
Dependencies
If the type has a "Blocked by" relation (as in the "Tasks" template), the timeline draws arrows from the end of a blocker to the start of the task it blocks.
An arrow is highlighted if the blocker ends later than the dependent task starts — the bar's tooltip then shows "The blocker ends after this starts". That's a cue to move one of them.
Which relation counts as a dependency: the one set in the saved view; otherwise the relation with the key
blocked_by; otherwise a many-to-many relation of the type to itself in which cycles are forbidden.Up to 50 blockers are taken into account per object.
You can't create relations by dragging between bars: blockers are added in the card, in the "Relations" block. Moving a blocker doesn't shift dependent tasks automatically.
Milestones
If the workspace has a "Milestone" type (key milestone, as in the "Tasks" template) with a date field, a "Milestones" row appears above the objects: each milestone is a diamond on its date. Clicking a diamond opens the milestone.
Filters and views
The timeline uses the same "Filters", search and "Assignee" filter as the table, board and calendar; the conditions are kept when you switch tabs. You can save the filters together with the scale and grouping as a view with the "Save as view" icon on the toolbar. In the list of views, timelines are collected in the "Timelines" group. If you changed the settings of a saved view, click "Update view". Flow remembers the last view you opened for a type, including the timeline.
For more on filters and views, see Flow: table, board, calendar and filters.
Limits
The timeline shows up to 1,000 objects. If there are more, you see "Showing the first 1000 items. Narrow the filter."
The scale scrolls without reloading: objects are loaded once, with the filters applied.
There is no critical path, no baselines and no automatic shifting of dependent tasks.
On a phone
On a narrow screen the name column is narrower and you scroll the scale with your finger. A touch scrolls the screen and doesn't drag bars, so you don't move a due date by accident. On a phone it's easier to change dates in the object card; tapping a bar opens it.
Dragging and ranges in the calendar
You can also move objects with the mouse in the calendar:
Drag an object's marker to another day — the date field by which the object appears on that day changes. For a "Date and time" field the time is kept; if there was no time, 9:00 is set.
Ranges. If the type has "Start date" (
start_date) and "Deadline" (due_date) fields and both are turned on in the field switcher, an object with both dates appears in the calendar as a single bar across all days from start to due date. Drag the bar and both dates move by the same number of days.On a narrow screen, bars are shown as markers on each day of the range.
Dragging in the calendar works only with a mouse. Everything else about the calendar — zoom levels, date fields, creating an object by clicking a day — is in Flow: table, board, calendar and filters.
What's next
Flow: table, board, calendar and filters — the type's other views and filters.
Flow: subtasks, checklists and tags — how to break a task into parts.
Flow: the object card — "Blocked by" relations and the other fields.
Flow API: objects, transitions and relations — how to change dates and read relations through the API.
Comentarios