We’re improving the Jira Business project timeline so it’s easier to see how work is progressing at a glance.
Two changes are rolling out:
Roll up: parent items automatically reflect the dates and status of their child work (including subtasks).
Field columns: key fields like assignee and status stay visible as you scroll the timeline, and can be edited inline.
These changes give you better project visibility and reduce manual updates on epics and other parent items.
Roll up is how Jira automatically summarizes key details from child issues and shows them on their parent in the timeline. Visually they are represented in thinner timeline bar and arrow indicator on hover.
When roll up is enabled:
The parent’s dates are calculated from its children:
Start date = earliest child start date
End date = latest child end date
The parent shows overall progress, based on the statuses of its children.
You can still edit dates, status, assignee, and summary inline on the timeline, but you don’t have to manually keep parent dates in sync with child work.
We show hidden done items in roll-up values because roll-up should display a single source of truth. Let us know if you think otherwise.
This helps you:
See if parent items are realistically scoped based on the underlying work.
Spot schedule risk quickly when child work drifts beyond the original dates.
Keep stakeholders focused on the big picture instead of clicking through every child issue.
Sometimes Jira can’t fully determine a parent’s schedule because some child issues are missing dates. That’s where partial roll up comes in. Visually they are represented in a zigzag bar.
Partial roll up happens when a parent has child issues, but one or more children don’t have start and/or end dates. It’s a signal that the parent’s timeline is based on incomplete data and may not represent the full scope.
To get a complete roll up, make sure all relevant child issues have both start and end dates.
To keep timelines fast and to avoid misleading summaries, roll up is disabled in a few situations:
The parent has no child issues
With no children, there’s nothing to roll up from.
You can still set and manage the parent’s dates manually.
The space contains more than 10,000 issues
For very large spaces, calculating roll up across all items can add noticeable delay.
To protect performance, roll up is turned off when a space exceeds 10,000 issues.
The timeline still works as usual; parent items just don’t auto-calculate from children’s fields.
A flat layout is active (for example, in certain filtered/search views)
Roll up is designed for hierarchical views where you can see parents and children together.
When the timeline is displayed as a flat list of items with no visible hierarchy, roll up is disabled to avoid confusion.
Alongside roll up, we’re adding field columns to the Business project timeline.
Let you edit those fields inline directly from the timeline.
Make it easier to scan who’s responsible and what status work is in, without opening each issue.
These changes to the Business project timeline aim to:
Reduce manual work keeping parent issues in sync with child items.
Improve visibility into project progress and risk at a glance.
Support inline updates, so you can manage projects directly from the timeline rather than switching between views.
If you’re already using Business project timelines, these updates should feel familiar, but more powerful—helping you track and communicate progress more confidently without changing how you structure your work
If you’re interested, please contact me directly here or leave your email in the comment section.
Amy Cheong
3 comments