the honest guide
How to make a Gantt chart in Jira
Jira has no button marked "Gantt" — but the Timeline view is the real thing under a plainer name, backed by your actual issues and free on every plan. It speaks agile, though, and it flags a slipped date without fixing it. Here's how to draw one, and where it stops.
We use the same six-week bakery-website plan as our worked examples, our Notion guide, and our Excel guide, so you can line them all up side by side.
before you start
A Jira timeline is your issues, drawn — but it thinks in epics and sprints
This is the difference that shapes everything else. A PowerPoint Gantt chart is a picture; a spreadsheet one is bars faked from numbers. A Jira timeline is neither — like Notion's Timeline view, it's a live view of real records, so the bars are dates, not pixels. The catch is the vocabulary: Jira doesn't think in tasks and milestones, it thinks in epics and sprints. Each phase of your plan becomes an epic; the bar is the epic's date range.
The raw material is the same as every other method: one row per phase, with a start date and a due date — and its duration is just the distance between the two. In Jira, that row is an epic in your backlog:
| Epic | Start date | Due date | Duration |
|---|---|---|---|
| Design | Apr 1 | Apr 14 | 14d |
| Build | Apr 8 | Apr 25 | 18d |
| Copy | Apr 18 | Apr 24 | 7d |
| Photos | Apr 22 | May 1 | 10d |
| QA & fixes | May 2 | May 12 | 11d |
method 01 — the native way, free on every plan
The Timeline view, in five steps
No trick, no invisible series, no hand-drawn rectangles. You create an epic per phase, give each one a date range, and the view you already have draws them. What you get is a genuine Gantt chart: a list of epics on the left, bars on a date grid to the right, sprints marked across the top.
-
Open the Timeline view
In any project, click Timeline in the left sidebar. It ships on every plan, free tier included. What opens is a real view of your issues on a date axis — not a picture you draw, but your backlog seen sideways through time.
-
Add an epic for each phase
Each bar on a Jira timeline is an epic — the closest thing Jira has to a Gantt "task group." Create one per phase of the plan: Design, Build, Copy, Photos, QA. Child issues nest underneath, but the phase-level bars are what read as the chart.
-
Give every epic a start and a due date
A bar needs two ends. Drag an epic's edges on the timeline, or open it and set Start date and Due date. With no due date an epic has no width — it shows as a stub, which is Jira's way of saying "this has no end yet."
-
Set the scale and switch on sprints
Use the Weeks / Months / Quarters switch (top-right) so the whole plan fits on screen. Turn on Sprints and Releases from the view settings to draw the agile furniture — fortnight columns and release markers — across the axis.
The list and the bars are the same epics, seen two ways. Drag a bar and its dates change on the issue; edit the dates and the bar moves. It's one plan, live — not a picture of one.
the part that surprises people
Jira flags a slip — it won't fix it
You can draw dependencies on the timeline: hover the edge of a bar until a dot appears and drag a line to the epic that waits on it — Build waits on Design, most links finish-to-start. But here's the honest surprise, and the one thing to plan around: when a date slips, native Jira does not move the dependent epic for you. It turns the dependency red to say the dates now conflict, and leaves the bar exactly where you put it.
the plan as agreed
Build is timed to start the day Design ends. The dependency is happy.
Design slips 5 days → Build turns red, but stays put
Build now starts before Design finishes. Jira flags the clash — and waits for you to drag Build yourself.
That's the exact opposite of Notion's Timeline, which shifts everything downstream on its own, and of a tool like ganttchart.ai, where a slip reflows the whole critical path. Jira's Premium tier (Jira Plans, formerly Advanced Roadmaps) adds an explicit auto-schedule button that can push dependents in one pass — but it's a deliberate action you run, not a plan that keeps its own promises. On the free timeline, keeping the dates honest after a slip is hand work.
the paid tier — when one project isn't enough
Jira Plans (Advanced Roadmaps), and what it does and doesn't add
The free Timeline draws one project. When you need to see many projects and teams on a single plan — with capacity, cross-project dependencies, and that auto-schedule pass — that's Jira Plans, included with Premium and Enterprise (it used to be called Advanced Roadmaps). It's a genuine step up for planning a whole portfolio.
What it doesn't add is telling. Even on Premium, Jira has no true milestone marker, no critical-path highlighting, and no baseline to compare the plan against where it started. If those are the features you came for, you're looking at a Gantt-chart Marketplace add-on layered on top of Premium — a second subscription for the three things people most often mean by "a real Gantt chart."
the honest part
Where Jira's timeline stops
It's a real, data-backed timeline — a strong one if your work already lives in Jira. It's also shaped for agile delivery, not classic scheduling. Four honest edges to know before you commit a plan to it:
- It flags, it doesn't fix. A slipped date lights up the dependency red but never reschedules the work waiting on it. Keeping the plan honest after a change is manual — the reverse of a tool built to reflow.
- It speaks epics and sprints. The bars are epics, the columns are sprints. If your plan isn't shaped like agile delivery — a launch, a renovation, an event — you're bending your work to fit Jira's grammar.
- No milestones, critical path, or baselines. Not on free, not on Premium. The three things people most associate with a Gantt chart all live behind a Marketplace add-on you pay for separately.
- It only pays off if you already live there. The magic is that the plan sits on top of your real issues. If your team isn't in Jira, standing up a project just to draw one chart is a heavy way to get a picture a template or a sentence would hand you in a minute.
None of that makes Jira the wrong call — if your delivery already runs on epics and sprints, the Timeline view is a real Gantt chart you don't have to leave your tracker for. It's when you want the chart, the milestones, and a plan that heals itself that Jira starts asking you to pay up or do it by hand. Our head guide compares every route side by side.
questions we actually get
Jira Gantt charts, answered
Does Jira have a built-in Gantt chart?
Not under that name — Jira calls it the Timeline view (it was briefly "Roadmap"). Give each epic a start and a due date and Jira draws one horizontal bar per epic along a date axis: a Gantt chart in everything but the label, and available on every plan including the free tier. The difference from a spreadsheet is that the bars are your real issues, so they are dates, not pixels.
Do I need Jira Premium (Advanced Roadmaps / Plans) for a Gantt chart?
No — the single-project Timeline is free. Premium adds Jira Plans (formerly Advanced Roadmaps): the same idea stretched across many projects and teams, with capacity planning and auto-scheduling. It's worth it for planning a whole portfolio, but it still doesn't add milestones, a critical path, or baselines. For those you need a Marketplace add-on on top of Premium, which is a second bill.
Does a Jira timeline reschedule dependent issues when one slips?
No, and this is the part to plan around. Native Jira flags a dependency conflict — the badge on the dependency turns red — but it will not move the dependent issue for you. If Design overruns, Build stays exactly where you put it and simply lights up as conflicting. That's the opposite of a tool like Notion's Timeline, which shifts everything downstream automatically. Jira warns; it won't fix.
How do I add a milestone to a Jira timeline?
Natively, you fake it. Jira has no zero-width milestone diamond, so people use a Release marker on the axis, or a single-day issue named for the moment ("Launch," "Sign-off"). A true milestone marker — the kind that sits on the line as a diamond — only comes from a Gantt-chart Marketplace add-on.
What's the fastest way to make a Gantt chart?
Describe the plan in a sentence and let ganttchart.ai draw it — tasks, durations, dependencies, and milestones included — in about ten seconds, as a shareable link. Building it in Jira means creating epics, dating each one, and wiring up dependencies first, and even then the plan flags slips instead of fixing them. Worth it if your team already lives in Jira; slower than a sentence if the chart is all you need.
New to the vocabulary? Every planning term on this page is defined in the plain-English glossary.
Want the chart to fix itself?
Describe your project in plain English and get a shareable, editable Gantt chart in seconds — dependencies and milestones included, and a slip reflows the whole plan instead of just turning red. No epics to wire up first.