The Timeline tab draws a project's tickets against a calendar: one row per ticket that has a start or due date, sub-tickets under their parent, and a bar from the start date to the due date. It is a Gantt chart made from the dates already on the tickets. There is no separate plan to maintain, and nothing is stored beyond the ticket dates themselves.
Before you start
The tab is off by default. An Owner, Admin, or workspace-user Project manager turns it on under the project's Settings tab with Show a Timeline tab (Gantt). Anyone who can see the project can then read the timeline; moving a bar changes the ticket's dates, so that needs the right to edit the ticket (full project members, Owners, and Admins). Regular client users do not see the tab, since they cannot see a project's ticket list.
Steps
- Open the project and select Timeline.
- Choose the scale with Zoom (Days, Weeks, Months). The calendar always fills the chart's width in whole weeks, so a short plan still shows the weeks after it. Today scrolls the chart to the current date, marked by a vertical line.
- Select the small triangle in front of a parent to hide or show its sub-tickets. Select a ticket's title to open it.
- To move a ticket in time, drag its bar sideways and release; to change one date, drag the left or right end of the bar. With the keyboard, focus a bar and use the arrow keys: ← and → move it a day, Shift+←/→ a week, Alt+←/→ change the due date.
- When you move a parent that has sub-tickets, a dialog asks Move it 3 days later with a checkbox, Also move its 4 sub-tickets by the same number of days. Your choice is remembered for the rest of the session. Select Move.
What the chart shows
- Rows. Every ticket in the project with a start or due date, plus every parent of one so the tree holds together. A parent without dates of its own is drawn with its sub-tickets and the note "no dates of its own". Archived tickets are left out. Tickets are ordered by their first date; sub-tickets sit under their parent, indented. Each row shows the ticket id, the title, the assignee, and the state.
- Bars. A ticket with both dates is a bar from the start to the due date. Open tickets are drawn in the brand colour, closed tickets in grey with the title struck through, and an open ticket past its due date has a red border ("Overdue" in the legend). A ticket with only a due date is a diamond on that day; a ticket with only a start date is a short dashed bar that begins there.
- Progress on a bar. For workspace users, a bar that is wide enough carries one figure. When the ticket has an estimate and logged time, it is the share of the estimate that is logged, for example "40 %" (it passes 100 % when more is logged than planned). When time is logged but there is no estimate, it is the logged time, for example "2 h 30". A ticket with no logged time carries nothing. For a parent, the estimate is the sum over its sub-tickets on this timeline, as on the ticket page, and the logged time is its own plus theirs; sub-tickets in another project are not counted here. Client users, elevated or not, never see estimates or logged totals, so their bars carry no figure. The same figure is in the bar's tooltip and its accessible name.
- Span of sub-tickets. Under a parent's own bar, a thin, pale line runs from the earliest to the latest date of its sub-tickets, at any depth ("Span of the sub-tickets" in the legend). Where that span runs outside the parent's own dates, the line turns amber, and the row carries a warning icon ("Outside the parent ticket's dates"). This is the same soft rule as on the ticket page: allowed, but visible. See Link tickets.
- Visibility. You only see tickets you may see. A parent in another project, or one you may not see, is not shown; its sub-tickets appear as top-level rows. Nothing hints at what is hidden.
- Limit. A project with more than 2 000 non-archived tickets shows the first 2 000 by start date and says so above the chart.
Rules
- Moving keeps the distance. Dragging a bar moves the start and the due date by the same number of whole days. Dragging one end moves that date only; a start cannot be dragged past the due date, or the due date before the start.
- Sub-tickets move only when asked. Moving a parent never moves its sub-tickets silently. The dialog's checkbox decides, and its state is kept for the session (the box starts unticked in a new session). Sub-tickets you cannot see are never moved.
- Every move is an ordinary edit. Each ticket's dates change through the same rules as on the ticket page: the edit is recorded in the ticket's history ("set the start date to", "set the due date to"), the start date must not end up after the due date, and archived tickets are refused. A ticket you may not edit, or an archived one, is left where it was and named in the message: "Moved 3 tickets. 1 ticket was left unchanged because you cannot edit them or they are archived: ACME-212."
- Recurring tickets keep their dates. A sub-ticket created by a recurring series takes its dates from the rule; moving its parent leaves it where it is and lists it among the tickets left unchanged.
- One project at a time. The timeline shows one project. Sub-tickets in another project are not drawn here and are not moved with their parent.
- Reading is free of side effects. Opening the tab changes nothing.
Examples
A release: ACME-200 Release 3.2 runs from 1 to 31 October and has four sub-tickets. One of them, ACME-207, is due 4 November, so the span line under the release turns amber at the end and the row of ACME-207 shows the warning. The project manager drags the release bar a week later and ticks Also move its 4 sub-tickets; every date moves seven days and each ticket's history records the change.
A support project never turns the tab on: its tickets have due dates but no plan, and the board is the better view.
Through the API
GET /api/w/acme/projects/web/timeline returns the rows (items, each with id, humanId, title, state, parentId when the parent is on the same timeline, startDate, dueDate, assignee, closedAt, and, for workspace users, the ticket's own estimateMinutes and loggedMinutes; both are null for client users), truncated, and canEdit. POST /api/w/acme/tickets/ACME-200/shift with {"days": 7, "includeChildren": true} moves the dates and answers with moved and skipped ticket ids. Both are browser-session operations; API tokens change dates through PATCH /api/w/{slug}/tickets/{ref} instead. See Projects and Tickets.
Common problems
- There is no Timeline tab. The project has not turned it on; ask an Owner, Admin, or the Project manager to tick Show a Timeline tab (Gantt) under Settings.
- "No ticket on this project has a start or due date yet." Set a start or due date on a ticket and the row appears.
- The bar does not move. You may not edit the ticket's dates (you are not a full member of the project), or the ticket is archived.
- A sub-ticket is missing. It is in another project, archived, or one you may not see.