Jira does not include a native Gantt chart feature, and making a Gantt chart in Jira therefore means exporting your task dates and rendering them in a separate, browser-side timeline tool. Jira's own Timeline view is the closest built-in equivalent, but it lives inside Jira, cannot be exported as a true chart file, and gives you no way to attach the result to a slide deck, an executive wiki page, or a status email. The lightweight workaround is to copy your issues out of Jira as simple task,start,end rows, paste those rows into a deterministic local renderer such as Gantt Chart Maker, and download the result as a self-contained SVG that shows the same bars you saw in the preview. The schedule never leaves your browser tab, no Jira Gantt plugin has to be installed, and each bar reflects the inclusive day count of its task rather than a fuzzy approximation of when work might happen.
Why Jira doesn't ship with a real Gantt chart
Jira is built around issues, sprints, boards, and workflows rather than around a Gantt schedule. Its Roadmap view and Timeline view are horizontal schedule visuals, and at a glance they look very much like a Gantt chart — task names down the side, horizontal bars stretching across calendar dates. The catch is what they don't show: there are no dependency arrows, no progress percentages, no critical path, and no way to export the layout as a portable chart file. Those views are rendered from Jira's own schema, which means moving the same schedule to a slide deck still requires either a screenshot or a paid Marketplace add-on.
That gap is exactly why articles about "making a Gantt chart in Jira" almost always describe one of three workarounds: rely on the built-in Timeline view, install a paid Gantt plugin, or rebuild the schedule in a separate tool. The first option gives you only what Jira already shows. The second works but adds cost, permissions to manage, and a license you have to renew. The third hands you the most control as long as the destination tool can ingest a clean schedule in a simple, predictable format.
Three paths to a Jira Gantt timeline
| Approach | Cost | Jira admin install | Exportable as a chart file | Best fit |
|---|---|---|---|---|
| Jira Timeline view | Included with Jira | No | Screenshot only | A quick in-product visual that stays in Jira |
| Marketplace Gantt plugin | Paid subscription, varies by app | Yes | Depends on the plugin | Teams that need live sync and dependencies |
| Browser-side tool with exported rows | No subscription | No | Standalone SVG download | A clean chart that can be shared outside Jira |
The third row is the path most readers searching this query end up taking. It trades live two-way sync that plugins offer for portability, privacy, and a chart you can attach anywhere. If your schedule is stable enough to copy into a short CSV-style block, this is typically the fastest answer for a status update or a kickoff deck.
Exporting Jira tasks as task,start,end rows
The browser tool speaks CSV-lite: each task line is exactly task,start,end with two literal commas between the three fields. To get there from Jira, you only need three columns from your project: the issue summary, the start date, and the due date or end date. The fastest way is Jira's built-in CSV export from the issue navigator, but copying the columns you care about into a spreadsheet works just as well for smaller backlogs.
Clean up the rows until each non-empty line contains exactly those three fields:
- Task label — keep each task label to 80 UTF-16 code units or fewer. A label over the limit is rejected without truncation, and literal commas are unsupported because the parser treats them as field separators.
- Start date — set every start to a real UTC calendar day in exact YYYY-MM-DD form. Jira's date picker already gives you a calendar day, so this is mostly a formatting step.
- End date — pull from the Due field or any custom end-date field, and confirm the format matches your start column byte-for-byte.
Once your spreadsheet has only those three columns and one row per task, copy the whole block out. Two to thirty non-empty rows fit comfortably for most sprints and small projects. Longer plans should be split, because the tool's deliberate choice is to refuse the input rather than silently truncate over the thirty-row ceiling.
Building the Gantt chart in your browser
- Open the Gantt Chart Maker page in the same tab where you'll do the rest of the work, so nothing has to leave the browser to generate the chart.
- Optionally type a short title into the title field — any plain text under about a hundred characters works as the chart heading.
- Paste your task rows into the schedule area. One task per non-empty line, in task,start,end form, with both dates in exact YYYY-MM-DD form and the end on or after the start.
- Click Generate. The renderer rejects the whole submission on any single malformed row, so if you see an error message, fix that row before retrying — no partial charts are ever returned.
- Inspect the preview and confirm each bar starts where you expect, that every inclusive end date lands on the rightmost occupied cell, and that the tick labels match the day or month range of your project.
- Click Download SVG. The file you receive is the exact string that produced the visible preview, so what you see is exactly what gets shared.
Date rules the browser tool enforces
The chart measures calendar occupancy, not work effort, so the dates drive everything that is drawn. A handful of rules are worth understanding before you paste anything:
- End dates are inclusive. A task starting January 1 and ending January 3 occupies three day cells — January 1, 2, and 3 — and a same-day task occupies exactly one.
- Dates are validated as real proleptic Gregorian UTC calendar dates, not as loosely parsed strings. April 31, February 29 in a non-leap year, and a missing zero like 2024-1-5 all fail before any drawing happens.
- The horizontal axis runs from the earliest task start to the day after the latest inclusive task day. Every bar's width equals that task's inclusive day count, and bar positions are whole UTC-day offsets measured from the earliest start.
- Spans of 62 days or fewer draw deterministic day ticks. Longer spans step out to month ticks so the axis stays readable. All tasks and their full date widths still appear — only the labels change.
Compared to a Jira Timeline screenshot, the SVG bars are deliberately flat rather than draggable. The output is a snapshot you can share, not an editable schedule that knows about Jira permissions.
Verifying the preview and downloading the SVG
The same string that drives the preview also drives the download, so verification is short. After generating, scroll across the rendered chart in the preview and check that each task label appears on its own row, that the leftmost bar lines up with the earliest start date, and that the rightmost bar reaches the latest end date. The exported SVG follows the W3C SVG 2 specification, includes the title you typed, and embeds accessible role and aria-label nodes so screen readers can describe it.
If a label runs long, or the chart is simply wider than the preview frame, the preview scrolls horizontally instead of shrinking text into a squeezed mobile width. The downloaded SVG keeps the full logical width and a matching viewBox, so downstream tools, slides, and wikis render it at the dimensions you intended rather than at whatever the preview happens to allow.
When a dedicated project tool is the next step
A deterministic SVG is a useful artifact, but it isn't a project-management system. For dependency planning, resource capacity, audit history, permissions, and live two-way sync between the chart and the underlying Jira issues, treat the browser path as a fast export target rather than a replacement for Jira itself. The approach is well suited to status updates, kickoff slides, executive one-pagers, and review meetings where a clean image of today's plan is what actually matters — and where the schedule is small enough to capture as task,start,end rows.