Use Gantt planning on a proportional time axis to see when work starts, how long it runs, and where the gaps are.
Find the controls
The timeline starts in Board Structure → Columns or Rows, not in the date-ruler menu. Select a date-bearing dimension and use its Switch to timeline control beside the coverage badge.
The Sprint row has a Switch to timeline control beside its coverage.
The canvas toolbar has separate card-content and date-ruler controls. The numbered circles identify controls, not steps.
Find card content and date controls. The numbers identify controls, not steps.
- 1. Edit card content: choose the fields displayed inside cards.
- 2. Date ruler: choose how the calendar scale is displayed on a timeline.
Create your first timeline
For a first timeline, use a source with dated Sprints. In Board Structure → Columns, add Sprint, then select that dimension’s Switch to timeline control. Look for dated Sprint bands and an Unscheduled area for work without usable dates. Optionally add Team to Rows if that field is available in your source. Select a Sprint header and open Inspector to review the work in it.
Enable your first timeline
- Choose the planning level above the canvas before editing its structure. This example uses Epic.
- Open Board structure → Columns. Add Sprint, or change the existing Columns field to Sprint if you are replacing a Status-column example. Keep just one dimension on this axis.
- Select the Sprint row’s Switch to timeline button, beside its coverage badge. Hover over the button first if you need to identify it.
- Check that the button becomes active and Sprint bands appear across the board. The example keeps Project in Rows; adding Rows is not required to turn on the timeline.
Sprint bands span the board above Project rows. Undated work stays separate.
The enlarged result shows Sprint bands and their separate Unscheduled area, not a date ruler or readable card details. Use the date-ruler examples below to read calendar dates. To return to ordinary columns, select the active timeline button again.
If the control is unavailable, check that the axis has just one date-bearing dimension and that the loaded values have usable dates. The reference below explains eligibility, ancestor placement and compressed timelines. A Compressed timeline is ordered by date but its band spacing is not proportional to calendar duration.
When you assign a date-bearing field as a board dimension, Board Studio turns the board into a Gantt-style timeline. Any field that carries dates can drive it: Sprint, Fix Versions, or a custom field that exposes start and end dates. Cards are placed and sized along a time axis, which gives you a temporal view of the plan.
An axis can use a timeline when it has one date-bearing dimension, either an interval (a start and an end) or a point (a single date), and the data provides usable dates. Use the dimension’s Switch to timeline control in Board structure to enable it. Timeline settings appear beneath the active dimension. Replacing its field resets the timeline setting so the new field is evaluated on its own.
Sprint headers, Team rows and rolled-up links provide a cross-team overview.
Supported fields
| Field | Type | Date source |
|---|---|---|
| Sprint | Interval | startDate and endDate from the Jira sprint. |
| Fix Versions | Interval or point | startDate and releaseDate for an interval, or releaseDate only for a point. |
| Custom fields | Interval | Any field that exposes a { startDate, endDate } object. |
| Date or DateTime fields | Point | A single date mapped to one position on the axis. |
A Fix Version with both a start and a release date renders as an interval band. With a release date only, it renders as a point.
Date eligibility does not make every value a valid interval. Malformed dates, a finish before the start, or an incomplete supplied interval remain Unscheduled. Equal valid start and finish dates represent a point. Board Studio does not invent a missing finish date to make a card look scheduled.
How it works
When a date-bearing field is used as a dimension, Board Studio reads the date ranges from the field, creates time-proportional bands where each interval takes space in line with its calendar duration, and places and sizes the cards inside their band. A two-week interval’s cards are half the width of a four-week interval’s cards.
Band width
Board Studio uses two scaling strategies, depending on the total span.
Calendar mode (the default, for spans under 5 years)
Band width is proportional to calendar duration, on an adaptive pixels-per-day scale:
| Total span | Pixels per day |
|---|---|
| Up to 42 days (about 6 weeks) | 32 |
| Up to 84 days (about 12 weeks) | 25 |
| Over 84 days | 18 |
A minimum band width of 260 px keeps even very short intervals usable.
Bucketed mode (automatic, based on readability)
When the shortest interval would render narrower than 80 px after fit-to-view, Board Studio switches to bucketed mode. Every interval then gets a fixed-width column regardless of its calendar duration, so a 1-year sprint and a 10-year sprint take the same width. The check uses the real viewport size and the ratio of the shortest interval to the total span, so it behaves correctly on any screen.
| Aspect | Calendar mode | Bucketed mode |
|---|---|---|
| Turns on when | Shortest interval is at least 80 px on screen. | Shortest interval is under 80 px on screen. |
| Band width | Proportional to duration. | Fixed per band. |
| Date accuracy | Proportional to the day. | Piecewise within each bucket. |
| Best for | Uniform sprint cadences. | Uneven intervals and historical data. |
For example, a dataset with two-week sprints next to a six-month sprint would render the two-week columns far too narrow in calendar mode. Bucketed mode gives every interval an equal column while keeping the order.
Date ruler
A date ruler runs along the timeline axis, between the field-name label and the band headers. It gives the timeline an explicit scale instead of relying on tooltips alone.
The ruler adapts its level of detail to how much room each day has on screen. As you zoom, it moves between an overview, months, weeks, and days, and it thins out labels that would collide so they stay readable. A marker shows today’s date. In bucketed mode it shows a Compressed timeline badge, since the spacing is no longer proportional to the calendar.
Use the Date ruler control in its own group on the canvas toolbar to choose Auto, Always or Off. It is separate from hierarchy visibility and card content; changing the ruler does not change the planning level.
| Mode | Behaviour |
|---|---|
| Auto (default) | Shows the ruler when an axis is in timeline mode. |
| Always | Keeps the ruler on. |
| Off | Hides the ruler. |
Sprint header bands retain each project cadence above the Epic timeline.
Each coloured band names a Sprint and spans its actual schedule.
Responsive cards
Cards adapt their display to the width available in their band.
| Mode | Width | Shown |
|---|---|---|
| Full | 220 px or more | The complete card: configured fields, avatars, rollup metrics. |
| Compact | 120 to 219 px | Key fields: the issue key and a status badge. |
| Chip | Under 120 px | A small badge with the issue key. |
Zoom in to widen bands and see full detail. Zoom out for a chip-level overview of the whole timeline.
Unscheduled band
Work without usable dates for that axis is collected into an Unscheduled area at the end of the timeline. This area represents missing scheduling information, not a time interval. Its physical size accommodates cards and groups; it is not guaranteed to stay at a fixed 180 px.
Place undated cards using ancestor dates
In Board structure → Timeline placement, enable Use ancestor dates for undated cards when an active timeline needs family context.
For each timeline axis, Board Studio first uses the card’s own usable dates. If it has none, it follows the loaded parent chain to the nearest ancestor with dates for the same field. If no suitable ancestor is available, the card stays Unscheduled on that axis.
This changes placement only. It does not write dates to Jira or turn the ancestor’s duration into the child’s duration. The Inspector identifies the ancestor and field supplying the placement. A card can use its own dates on one axis and ancestor placement, or Unscheduled placement, on the other.
Ancestor dates affect placement only, not Jira dates or duration.
Multi-sprint spanning
When a work item belongs to more than one sprint, its card spans from its earliest sprint to its latest. This works on both horizontal and vertical timeline axes, which gives a true Gantt bar for the item’s lifespan.
Jira’s sprint field is an array that keeps sprint history. When a sprint completes with an issue still in it and the issue moves on, both sprints stay in the array. Board Studio reads the full array to compute the span, from the earliest historical sprint to the most recent.
| Axis | Effect |
|---|---|
| Horizontal | Card width stretches from the earliest to the latest sprint column. |
| Vertical | Card height stretches from the earliest to the latest sprint row. |
Cards that belong to a single sprint render at standard size. Spanning only happens when several sprints are present.
Completed sprint horizon
By default the timeline shows the two most recent completed sprints plus any active or future sprints, which keeps the view on current and upcoming work. When bucketed mode turns on, this filter is lifted so the full timeline is shown.
Viewport fill
If the whole timeline is narrower than the viewport, Board Studio stretches the dated bands to fill the space. The Unscheduled area stays after the dated content and reserves enough room for its cards rather than pretending to represent a calendar duration.
Cross-axis layout
The non-timeline axis keeps its grouping, which gives you a two-dimensional view: time on one axis, structure on the other. For example, place a Sprint timeline on one axis and Team on the other to coordinate Epics across teams and cadences without constraining the available timeline space.
Individual hierarchy-level views can use two timeline axes. Date placement and missing-date handling are evaluated separately on each. Global view supports one active timeline axis at a time.
| Timeline axis | Cross axis | Result |
|---|---|---|
| Horizontal columns | Team rows | Each row is a team; cards span time-proportional columns. |
| Vertical rows | Team columns | Each column is a team; cards span time-proportional rows. |
Select through timeline headers
Click a timeline header to select every card scheduled in that interval. The Inspector records the Sprint as a structural selection criterion and shows its real start date, end date, and state.
Shift-click more Sprint headers to add intervals. Sprint criteria combine as a union, so selecting BAC Sprint 3 and BAC Sprint 4 includes cards from either interval.
Selecting BAC Sprint 3 reveals its 1 to 19 November 2026 schedule and three matching Epics.
In this Northstar example, BAC Sprint 3 runs from 1 to 19 November 2026, and BAC Sprint 4 runs from 22 November to 10 December 2026.
Shift-click a header on the other axis to intersect it with the selected timeline intervals. For example, BAC Sprint 3 or BAC Sprint 4 combined with Payment Services selects only the Epics that match the chosen Team and either Sprint.
BAC Sprints 3 and 4 intersect with Payment Services to select BAC-14 and BAC-15.
The resulting intersection contains BAC-14 and BAC-15.
Stable fit-to-view
Clicking Fit to View zooms to show all content without recalculating the layout, so cards do not shrink on repeated fits. The viewport state is kept.
Works with other features
| Feature | Behaviour in timeline mode |
|---|---|
| Focus Mode | Focus a card to see its connections across time bands; multi-sprint cards show every spanned column. |
| Semantic Zoom | Zoom out for a chip-level overview; zoom in for full detail. |
| Dependency lines | Edges render across time bands to show cross-interval dependencies. |
| Rollups | Parent cards show rollup metrics within their band. |
| Dark mode | The timeline renders correctly in light and dark themes. |
Use cases
| Scenario | How the timeline helps |
|---|---|
| Sprint planning | See how work spreads across upcoming sprints, sized in proportion. |
| Release timeline | Use Fix Versions as the dimension to lay releases out by date. |
| Capacity check | Spot dense bands against sparse ones. |
| Cross-team coordination | Combine project rows with time columns to see allocation by interval. |
| Historical view | Use bucketed mode for long-range datasets that span years. |
Related
- Guided Tours and Contextual Help: choose the ruler or Board structure with Help to understand its controls without changing them.








