Last updated: April 2026
Map your work items to a proportional time axis — see when work starts, how long it spans, and where the gaps are.
Overview
When you assign a date-range field as a board dimension, Board Studio transforms the board into a Gantt-style timeline. Any field that carries date information can trigger timeline mode — Sprint, Fix Versions, or any custom field that exposes start and end dates. Cards are positioned and sized proportionally along a time axis, giving you a true temporal view of your plan.
Timeline mode activates automatically when an axis has exactly one dimension and that dimension is timeline-compatible — meaning the field is classified as an “interval” (has a start date and end date) or a “point” (has a single date). The data must also contain at least one item with actual dates.
Supported Fields
Timeline mode works with any field Board Studio classifies as date-bearing:
| Field | Type | Date Source |
|---|---|---|
| Sprint | Interval | startDate + endDate from Jira sprint data |
| Fix Versions | Interval or Point | startDate + releaseDate (interval), or releaseDate only (point) |
| Custom fields | Interval | Any field exposing a { startDate, endDate } object |
| Date / DateTime fields | Point | Single date value mapped to one position on the axis |
Tip: If a Fix Version has both a start date and a release date it renders as an interval band; if it only has a release date it renders as a point.
How It Works
When a timeline-compatible field is used as a dimension (horizontal or vertical), Board Studio:
- Reads date ranges from the field metadata (start date, end date, or release date).
- Creates time-proportional bands — each interval occupies space proportional to its calendar duration.
- Positions and sizes cards within their band, so a two-week interval’s cards are half the width of a four-week interval’s cards.
The result is a spatially accurate representation of your delivery timeline.
True Gantt-Style Layout
Unlike simple column-based boards where every band gets equal width, Board Studio’s timeline renders time-proportional bands:
| Aspect | Standard Board | Timeline Mode |
|---|---|---|
| Band width | Equal columns | Proportional to calendar duration |
| Card width | Fixed | Scales with interval duration |
| Time accuracy | None — visual only | Spatially proportional to real dates |
| Gap visibility | Hidden | Gaps between intervals are visible |
Band Width Calculation
Board Studio uses two scaling strategies depending on the total date span:
Calendar Mode (default — spans under 5 years)
Band width is proportional to calendar duration using an adaptive pixels-per-day scale:
| Total Timeline Span | Pixels per Day |
|---|---|
| ≤ 42 days (≈ 6 weeks) | 32 px/day |
| ≤ 84 days (≈ 12 weeks) | 25 px/day |
| > 84 days | 18 px/day |
A minimum band width of 260 px is enforced so that even very short intervals remain usable.
Bucketed Mode (automatic — readability-based)
When the shortest interval would render narrower than 80 pixels on screen after fit-to-view, Board Studio automatically switches to bucketed mode. In this mode, every interval gets a fixed-width column regardless of its calendar duration — a 1-year sprint and a 10-year sprint occupy the same visual width.
The detection uses the actual viewport size and the ratio of the shortest interval to the total date span: viewportWidth × (shortestDays / totalSpanDays). This viewport-aware approach ensures correct behavior on any screen size.
| Aspect | Calendar Mode | Bucketed Mode |
|---|---|---|
| Activation | Shortest interval ≥ 80 px on screen | Shortest interval < 80 px on screen |
| Band width | Proportional to duration | Fixed width per band |
| Date accuracy | Pixel-perfect proportional | Piecewise-linear within each bucket |
| Best for | Uniform sprint cadences | Non-uniform intervals, historical data |
Example: A dataset with 2-week sprints alongside a 6-month sprint. In calendar mode, the 2-week columns would be invisible next to the 6-month column. Bucketed mode normalizes all intervals to equal columns while preserving chronological order.
Responsive Card Modes
Cards automatically adapt their display based on the available width within their band:
| Mode | Width Threshold | What’s Displayed |
|---|---|---|
| Full | ≥ 220 px | Complete card — all configured fields, avatars, rollup metrics |
| Compact | 120 – 219 px | Key fields only — issue key and status badge |
| Chip | < 120 px | Minimal badge showing the issue key |
Tip: Zoom in to expand bands and see full card detail; zoom out for a chip-level overview of your entire timeline.
Timeline Visualization
Time-Proportional Bands
Each interval is rendered as a band whose width (or height, depending on axis) is proportional to its duration in calendar days. Band headers display the field value name and date range.
Unscheduled Band
Issues that have no value for the timeline field are collected into a virtual “Unscheduled” band at the end of the timeline. This band has a fixed width of 180 px and does not scale with the rest of the timeline. This ensures no work item is hidden — unplanned work is always visible.
Multi-Sprint Spanning
When a work item belongs to multiple sprints — for example, an issue that was active across several sprint cycles — its card visually spans from the earliest sprint column to the latest. This works on both horizontal and vertical timeline axes, giving a true Gantt-bar visualization of the work item’s lifespan.
How Jira Stores Multi-Sprint Membership
Jira’s sprint field is an array that retains sprint history. When a sprint is completed with an issue still in it, and the issue moves to the next sprint, both sprints remain in the array. Board Studio reads the full sprint array to compute the visual span — the card stretches from the earliest historical sprint to the most recent one.
Spanning Behavior
| Axis | Visual Effect |
|---|---|
| Horizontal timeline | Card width stretches from earliest to latest sprint column |
| Vertical timeline | Card height stretches from earliest to latest sprint row |
Cards that belong to only one sprint render at standard size within their single column or row — spanning only activates when multiple sprints are present.
Completed Sprint Horizon
By default, Board Studio shows only the 2 most recent completed sprints plus any active or future sprints. This keeps sprint-based timelines focused on current and upcoming work.
When bucketed mode activates (shortest interval too narrow for proportional display), this filter is automatically disabled so all sprints remain visible — ensuring the full timeline is displayed.
Viewport Fill
If the total timeline is narrower than the viewport, Board Studio stretches all dated bands proportionally to fill the available space. The Unscheduled band shifts to remain at the end but does not stretch — it stays at its fixed 180 px width.
Cross-Axis Layout
The non-timeline axis retains its spatial grouping. For example:
| Timeline Axis | Cross-Axis | Result |
|---|---|---|
| Horizontal (columns) | Project (rows) | Each row is a project; cards span time-proportional columns |
| Vertical (rows) | Team (columns) | Each column is a team; cards span time-proportional rows |
This gives you a two-dimensional view: time along one axis, organizational structure along the other.
Stable Fit-to-View
Board Studio’s timeline uses a stable fit-to-view algorithm that prevents the common “shrinking card” problem:
- Clicking Fit to View zooms the board to show all content without triggering a layout recalculation.
- Cards never shrink progressively on repeated fit-to-view actions.
- The viewport state is preserved — what you see is what you get.
Note: This is a solved engineering challenge. Some board tools suffer from a feedback loop where fitting to view causes cards to shrink, which changes layout, which requires re-fitting. Board Studio eliminates this entirely.
Works With All Features
Timeline mode is fully compatible with every other Board Studio feature:
| Feature | Timeline Behavior |
|---|---|
| Focus Mode | Focus on a card to see its connections across time bands — multi-sprint cards show all spanned columns |
| Semantic Zoom | Zoom out for chip-level timeline overview; zoom in for full detail |
| Dependency Lines | Edges render across time bands showing cross-interval dependencies |
| Rollups | Parent cards show rollup metrics within their time band |
| Dark Mode | Timeline renders correctly in both light and dark themes |
Use Cases
| Scenario | How Timeline Helps |
|---|---|
| Sprint Planning | See how work distributes across upcoming sprints with proportional sizing |
| Release Timeline | Use Fix Versions as the timeline dimension to visualize releases by date range |
| Capacity Visualization | Spot overloaded intervals (dense bands) vs. light intervals (sparse bands) |
| Cross-Team Coordination | Combine project rows with time columns to see team-by-interval allocation |
| Historical Visualization | Use bucketed mode to visualize long-range datasets spanning years or decades |