How to Build a Product Roadmap in Jira: Timeline

Jira ships with a roadmap. It is called Timeline, it appears in every Jira project out of the box, and it will be the wrong tool for the roadmap most product teams actually need — because Timeline shows epics inside one project, and a product roadmap is by definition a view across several.

That gap is where most of the confusion in this category lives, and it is where a lot of teams accidentally buy Jira Premium. This guide walks the whole path in order: build the single-project roadmap first, decide honestly whether it is enough, and only then model a cross-project hierarchy — while being explicit about the price of that last step, because the jump from Standard to Premium is $7.08 per user per month, not a small feature toggle.

If you have not settled on Jira yet, start with our roundup of the best project management software and our Jira review. If your team is still new to the tool, our Jira setup walkthrough for software teams covers the project configuration this guide assumes. And if you are weighing Jira against lighter options because the roadmap is what pushed you to look, Linear vs ClickUp is the comparison worth reading before you upgrade a plan. If your team never plans to live in Jira at all, our Nifty review covers the all-in-one option with roadmaps, tasks, and docs in one workspace.

TL;DR

Jira has two roadmap features, not one: the built-in Timeline/Roadmap view (epic-level, single project, available on Free and Standard) and Advanced Plans (formerly Advanced Roadmaps — multi-project, custom hierarchy above epics, capacity and dependency management, Premium and Enterprise only).
The roadmap you can build for free is a timeline of epics with finish-to-start dependencies in one project. That is enough for a single team. It is not enough for a product line.
Premium costs $15.56/user/month billed annually versus $8.48 on Standard — a delta of $7.08 per seat per month, which at 25 seats is $2,124 a year for the roadmap plus everything else Premium bundles.
Advanced Plans can add hierarchy above epics (initiative, theme, program). It cannot insert a level between epics and stories. Teams that need that go to an app in the Marketplace, not to a plan upgrade.
Best for: software teams already living in Jira who want the roadmap next to the backlog. If your roadmap is customer-facing and your team is under 10 people, this guide’s honest answer is: build it in Timeline, skip Premium.

Step 0: decide what “roadmap” means before you open Jira

Three different artifacts get called a roadmap, and they want different tools:

A delivery roadmap — when will these epics ship, sequenced against each other, owned by one team. This is Jira’s Timeline, and it is good at it.
A product roadmap — what themes and initiatives are we investing in across quarters, across teams, with dependencies between teams. This is Advanced Plans, or a dedicated roadmap tool.
A public roadmap — what have we committed to customers, sanitised and dated. This is neither of the above; Jira will fight you, and most teams publish it from a simple board or a Notion page.

Pick one. The most common failure we see is a team building a delivery roadmap in Advanced Plans because the name sounded right, then discovering they paid for capacity planning and scenario modelling to display eight epics.

Step 1: build the single-project roadmap (Free or Standard)

This is free, it takes about twenty minutes, and for a single team it is usually the whole answer.

1. Confirm your project type. Advanced Plans only works with company-managed projects. Team-managed projects — the default for a quick new project — have a Timeline, but their epics never appear in a cross-project plan. Check at Project settings → Details. If you have been running team-managed projects and intend to go Premium later, fixing this now is dramatically cheaper than migrating later; it is the single most expensive mistake in this guide.

2. Create the epics you actually plan in. A roadmap of twelve epics is a roadmap. A roadmap of ninety is a backlog with dates. Name epics as outcomes (“Checkout latency under 400ms”), not as components.

3. Set start and due dates on each epic. In the Epic panel or the epic’s own detail view. Epics without dates do not appear as bars — they sit in an unscheduled list at the bottom of the timeline, which is a usefully honest signal about your planning.

4. Open the Timeline. Your work → Timeline, or Planning → Timeline depending on your Jira version. Each epic renders as a bar spanning its start and due dates; its child stories appear beneath it as a mini-stack, which is what makes this view better than a spreadsheet: you see the delivery work density under each commitment.

5. Draw dependencies. Hover the right edge of a bar and drag to another bar. Only finish-to-start is supported on Standard. If your work needs start-to-start or finish-to-finish relationships, they exist on Premium, and that alone is sometimes the real reason a team upgrades — worth knowing before you attribute the upgrade to “the roadmap.”

6. Save the view. Jira lets you keep a configured timeline as a saved view; do it, name it after the audience (“Q1–Q2 delivery”), and share the link rather than a screenshot. Screenshots are how roadmaps become stale lies.

7. Put it in front of the people who need it. Add the timeline to a Confluence page if you use it, or to a dashboard. The roadmap’s usefulness is proportional to how often a non-Jira user sees it.

What you have now: epic-level sequencing, within one project, with finish-to-start dependencies. No capacity. No scenarios. No cross-project. For a team of three to eight engineers shipping one product, that is a real roadmap and you should stop here.

Step 2: know exactly what Premium buys

Before you click upgrade, here is the honest diff. Advanced Plans (the Premium capability) adds four things that matter for roadmapping, per Atlassian’s Jira pricing page:

Cross-project plans — one timeline over many Jira projects, filtered by JQL.
Custom hierarchy levels above epics — you can define initiative, theme, or program as levels above epic, and roll up dates and progress.
Dependency management across projects and cross-project capacity/scenario modelling — you can ask “what if we pull this initiative forward” and see the answer.
Release tracks and sandbox (useful, adjacent, not roadmapping).

And here is what it does not buy, which surprises people: a level between epic and story. Atlassian’s hierarchy is Epic → Story/Task/Bug → Subtask and Plans only extends upward. The community has asked for arbitrary nesting for years — the phrase that keeps recurring in Atlassian Community threads is that Epic “is locked at level 1” and users want infinitely nestable work items. Workarounds are issue links, which do not roll up and do not render as a tree, or Marketplace apps that reimplement hierarchy on top of Jira.

If your actual problem is “I want Feature under Epic,” Premium will not fix it and you will be paying $7.08 per seat per month to learn that.

Step 3: model the hierarchy (Premium)

If you have decided Premium is justified, do it in this order:

1. Define hierarchy levels at Settings → Issues → Hierarchy levels (site admin). Start with three above-epic-free defaults plus one you add, e.g. Initiative. Resist four. Every level you add is a field your team has to populate correctly forever.

2. Map levels to issue types. Initiative → Initiative issue type, Epic → Epic. If a level has no issue type mapped, it will never show up in a plan.

3. Create the parent issues. One initiative per bet, not per quarter. If you find yourself creating “Q3 Initiative” you are building a calendar, not a strategy.

4. Build the plan. Plans → Create plan, choose your project sources (or a JQL filter across projects), pick the issue sources, and set the hierarchy to include your new top level. Jira will warn you about unsaved changes; the plan is a working document, not a report.

5. Set the plan’s view fields — target start/end, status, and the team assignment. Team assignment is what makes capacity views and scenario modelling work; without it, Plans is a very expensive timeline.

6. Use scenarios, sparsely. Scenarios let you clone a plan and move dates without touching the actual issues. Useful for one quarterly planning conversation. Two scenarios nobody looks at again is the normal outcome.

What it costs at real team sizes

Jira Cloud pricing is per user, billed annually, and the published entry-band rates are $8.48/user/month for Standard and $15.56/user/month for Premium, with Free covering up to 10 users.

Seats	Standard/mo	Premium/mo	Premium delta/mo	Delta/year
10	$84.80	$155.60	$70.80	$849.60
25	$212.00	$389.00	$177.00	$2,124.00
50	$424.00	$778.00	$354.00	$4,248.00

Verified against Atlassian’s official Jira pricing page on 2026-10-22. Rates are the published entry-band figures, USD, annual billing; Atlassian applies continuous user-tier pricing, so effective per-user rates step down as seat counts cross higher bands, and Enterprise is quoted annually by sales and is not published.

The Free tier is genuinely usable here: up to 10 users, unlimited projects, 150 automation steps per subscription per month, 2 GB storage. A small product team can run Timeline on Free for a long time. The practical ceiling is the 10-user cap and the automation limit, not the roadmap.

One cost that does not appear in that table: Premium is per user, but roadmaps are read by managers. A 60-person engineering org that wants a portfolio plan pays Premium for all 60 seats, because Plans is a plan-level capability, not a per-person add-on. That is the moment the roadmap conversation becomes a budget conversation.

The team-size judgement call

If your team is under 10 people, build the roadmap in Timeline and stay on Free or Standard. You will not miss cross-project planning, because you have one project. You will not miss capacity modelling, because you know what everyone is doing. Save the $7.08 per seat per month and spend it on a dedicated roadmap tool the day you need a customer-facing view — you will get a better artifact for less.

If you are 10 to 30 engineers across two or more Jira projects with real inter-team dependencies, Premium earns its price. The dependency management and capacity views are the difference between “we think Platform blocks Checkout in March” and knowing it. At 25 seats that is $2,124 a year, which is less than one week of an engineer’s loaded cost — a defensible number, unlike many enterprise upgrades.

If you are past 50 seats, price out Enterprise before you commit to Premium. Enterprise is annual-only and quoted, and it bundles Atlassian Guard Standard, which you may be buying separately today. The listed per-user Premium rate is not the number your procurement team will see.

The mistake that costs the most

Migrating team-managed projects to company-managed. It is not a click. Issue keys can be preserved, but boards, automations, and any app that keyed off the project type are not. Multiple Atlassian Community threads describe teams that ended up relinking issues after a migration — and the migration was triggered, in the case of the clearest thread, by wanting Advanced Plans on projects that could not use it.

The lesson generalises: decide project type before you need the roadmap. If there is any chance your team will be on Jira Premium within two years, create company-managed projects now.

A second, cheaper mistake: setting dates on epics to make bars appear, rather than because you believe the dates. A roadmap full of invented dates trains everyone to ignore the roadmap. An honest roadmap with four scheduled epics and an unscheduled list of nine is a better artefact than a full picture you cannot defend.

What real teams say about the roadmap

The gap between Jira’s roadmap promise and what a team actually experiences is documented better in Atlassian’s own issue tracker than in any marketing page. On JRACLOUD-89064, the long-running request to make Advanced Roadmaps work with team-managed (“next-gen”) projects, users describe being stuck between two features they were told to adopt. One wrote that “it’s a little disappointing that your premium product doesn’t support what Atlassian suggests is the ‘better’ project type” and that the lack of support “is a disincentive for me to move to Premium.” Another put the cost decision bluntly: they were evaluating Premium, but “without advanced roadmaps the cost is not worth it.”

That is the most useful thing a buyer can read about this feature, because it is not a complaint about quality. It is customers doing the exact calculation this guide is doing — is the roadmap alone worth the plan upgrade? — and concluding, in public, that often it is not.

Two caveats on that evidence. It is a feature-request thread, so it selects for people who are unhappy, and the quoted comments date from 2020, before team-managed projects gained several capabilities. Treat it as evidence about the class of problem (plan-level features do not apply uniformly across project types), not as a current bug report.

A roadmap you can defend in a planning meeting

If you build nothing else, build these five things: epics as outcomes, dates you believe, finish-to-start dependencies where they are real, one saved timeline view per audience, and a rule that anything unscheduled is visibly unscheduled rather than quietly dated.

That roadmap fits on a Free Jira plan for up to ten people, and it will survive contact with a planning meeting better than a Premium portfolio plan nobody maintains. Upgrade when the cross-project question becomes real — and when it does, re-read the delta above, because at 25 seats you are signing up for $2,124 a year.

How this content was prepared

Transparency note: This guide is based on Atlassian’s official Jira pricing page (checked 2026-10-22), Atlassian’s own issue tracker at jira.atlassian.com (quotes linked inline), and published documentation of Jira’s hierarchy and Plans capability. It is not sponsored, and no vendor paid for or influenced the recommendations.

We do not claim to have independently tested Jira’s Advanced Plans end-to-end. The step sequence reflects the documented navigation and configuration model, not a recorded walkthrough of our own; screens and menu labels shift between Jira releases and between team-managed and company-managed projects, so where a label differs in your instance, the underlying setting is the same. We have not run a team-managed-to-company-managed migration, and our warning about relinking issues is drawn from public community accounts rather than our own measurement. Reddit’s Jira community was not retrievable for this article, so user evidence is limited to the Atlassian issue tracker linked above; we say that rather than summarising threads we could not open.