Jira Roadmap Guide 2026: Timeline View vs. Plans, Setup Steps, Dependencies, and Limits
Jira gives you two ways to build a roadmap. The Timeline view, included on every Jira plan, is a Gantt-style view of the work in one space (Atlassian’s new name for a project). Plans, formerly Advanced Roadmaps, comes with Jira Premium and Enterprise and combines work from many spaces, boards and filters, with capacity planning, cross-team dependencies and sandbox scenarios.
Most single teams only need Timeline. Program managers coordinating several teams need Plans.
Everything below comes from Atlassian’s support docs, checked October 12, 2026. A note on terms: Atlassian now calls projects spaces and issues work items, so you’ll see both sets of words in Jira.
Timeline vs. Plans at a glance
| Timeline view | Plans | |
|---|---|---|
| Included in | All Jira plans | Jira Premium and Enterprise |
| Scope | One space | Boards, spaces and filters combined, up to 200 spaces |
| Hierarchy | Epics and their child work items (2 levels shown when filtered) | Custom levels above epic, such as Initiative |
| Dependencies | Yes, within the space | Yes, including ones outside the plan, plus a Dependencies view |
| Capacity and velocity | No | Yes, by team |
| What-if scenarios | No | Yes; changes stay in the plan until you save them to Jira |
| Size limit | Roll-ups may switch off above 10,000 work items in a space | 10,000 work items per plan |
Sources: Timeline view, Timeline limits, What are plans, Limits on plan size.
Building a roadmap with the Timeline view
Open your space and select Timeline in the space’s sidebar. If it’s missing, an admin may have removed the view from the space.
- Create epics for the big pieces of work (for example “New checkout flow”).
- Add child work items under each epic, or link existing ones.
- Set start and due dates by dragging schedule bars. Bar colors show status.
- Let parents roll up. Atlassian says a parent’s start date becomes the earliest start date of its children, its end date the latest due date, and its progress reflects the children’s statuses. A parent with no children keeps the dates you set by hand.
- Add dependencies by dragging from one bar to another. Conflicting dates show up so you can fix them.
- Share it. Timeline is built for status updates with stakeholders, so filter to the epics that matter and walk through it in your review meeting.
Timeline limits that trip people up
- One space only. Company-managed boards built on a JQL filter that pulls from several spaces won’t show properly on the timeline. Atlassian’s fix is to narrow the filter to one space, or use Plans.
- Two levels when filtered. With inline hierarchy on and filters applied, the timeline shows level 1 (epics) and level 0 (stories, tasks, bugs) only.
- Huge spaces. Above 10,000 work items, Atlassian may switch off automatic roll-ups to keep the view fast.
Building a roadmap with Plans (Premium and Enterprise)
Plans is for “when will this land across all the teams involved?” questions. Atlassian’s overview lists what it adds: extra hierarchy levels like Initiative above epics, dependencies across the plan (even ones that live outside it), a sandbox where changes aren’t written to Jira until you choose to save them, capacity and velocity planning by team, and scenarios to compare versions of the plan.
- Create the plan from Plans in Jira’s sidebar and give it a clear name, such as “2027 H1 Platform Program.”
- Choose work sources: boards, spaces or filters. Keep them focused. A plan can load up to 10,000 work items and span 200 spaces, and Atlassian recommends excluding completed and irrelevant work to keep it fast.
- Set up the hierarchy. An admin can add levels above epic (for example Initiative) so programs roll up.
- Add teams and capacity. Atlassian recommends no more than 50 teams per plan.
- Map dependencies and check the Dependencies view for conflicts.
- Try scenarios (“what if the mobile team starts a sprint later?”) before committing.
- Review changes, then save the ones you want back to Jira work items.
Roadmap habits that keep it honest
- Roadmap items are outcomes, not tickets. Keep the roadmap at epic or initiative level; let sprints handle the detail.
- Dates come from children. If an epic’s bar looks wrong, fix the child work items rather than dragging the parent.
- Review dependencies every sprint. One slipped dependency is the usual reason a roadmap falls apart quietly.
- Use JQL filters to focus views. My JQL guide covers the queries that work well as plan sources.
- Report from dashboards, plan in the roadmap. For sprint-level reporting, see my Jira dashboards guide.
Do you need Premium for a Jira roadmap?
No, if you’re one team in one space; Timeline is included on every plan. Yes, if you need to plan across spaces, add levels above epic, or plan by team capacity. Before upgrading for Plans alone, check the current numbers in my Jira pricing guide and the fall 2026 Atlassian pricing changes. If your teams use Linear instead, compare its approach in Linear projects and roadmaps.
Common questions
Is the Jira roadmap free?
The Timeline view is included on all Jira plans, including Free. Plans, Jira’s cross-team roadmap tool, needs Jira Premium or Enterprise.
What happened to Advanced Roadmaps in Jira?
It’s now called Plans. It still comes with Jira Premium and Enterprise and adds cross-space planning, extra hierarchy levels, capacity and scenarios.
Can a Jira timeline show more than one space?
No. The Timeline view works with one space. To plan across spaces, use Plans in Jira Premium or Enterprise.
How many work items can a Jira plan hold?
Up to 10,000 work items, from up to 200 spaces, according to Atlassian.
How do epic dates work on the Jira timeline?
Parent items roll up from their children: the start date is the earliest child start, the end date is the latest child due date, and progress reflects the children’s statuses.
Checked against Atlassian Support documentation on October 12, 2026. Jira’s interface and naming change often, so menu labels may differ slightly in your site.
Sponsored
