How to Create a Gantt Chart in Jira (Step-by-Step Guide)

If you have ever tried to manage a complex project in Jira, you have probably hit a wall. Jira is excellent at tracking individual issues, but when you need to see the big picture — how tasks connect, which ones drive your deadline, and whether you are ahead or behind schedule — you need a Gantt chart.

This guide walks you through creating a fully-featured Gantt chart in Jira Cloud, step by step.

Why Jira Needs a Gantt Chart

Jira was built for issue tracking, not project scheduling. While it handles sprints, backlogs, and workflows well, it lacks the timeline planning tools that project managers depend on.

Here is what you typically cannot do in Jira alone:

• Visualize task dependencies across an entire project with all four relationship types
• Identify the critical path — the longest chain of dependent tasks that determines your project end date
• Save baselines to compare your original plan against actual progress
• See phases and milestones on a unified timeline
• Track project health with automated risk scoring

Jira does include a built-in Timeline view, but it is not a real Gantt chart. It supports only basic Finish-to-Start dependencies, offers no critical path analysis, and cannot save baselines. For simple projects, it works. For anything with real complexity, you need more.

What Jira Timeline Is Missing

Before jumping into the setup, it helps to understand the specific gaps:

Capability	Jira Timeline	Real Gantt Chart
Task bars on a timeline	Yes	Yes
Finish-to-Start dependencies	Yes	Yes
All 4 dependency types	No	Yes
Critical path highlighting	No	Yes
Baseline snapshots	No	Yes
Sprint overlay	No	Yes
Cross-project visibility	No	Yes
Project health scoring	No	Yes

If your project has more than a handful of tasks with dependencies, a Gantt chart is not optional — it is essential.

Step-by-Step: Setting Up Simple Gantt

Simple Gantt is a Forge-native Gantt chart for Jira Cloud. It runs directly on Atlassian’s infrastructure, so there is nothing to host and no data leaves your Jira instance. Here is how to set it up.

Step 1: Install from the Atlassian Marketplace

Find Simple Gantt on the Atlassian Marketplace and click Install. Since it is a Forge app, installation is a single click — no server configuration, no OAuth tokens, no admin headaches. The app is free to get started with no credit card required.

Once installed, Simple Gantt appears in your Jira project sidebar.

Step 2: Create Your First Gantt Project

Open Simple Gantt and create a new project. You will need to:

1. Name your project — this can match your Jira project or represent a cross-project initiative
2. Define your JQL query — this determines which Jira issues appear on your Gantt chart
3. Map your fields — connect Jira fields (start date, due date, story points) to the Gantt chart using custom field mapping

The JQL query is powerful. You can pull in issues from a single project, multiple projects, specific sprints, or any combination that JQL supports.

Step 3: Add Dependencies

With your issues on the timeline, it is time to add dependencies. Simple Gantt supports all four standard dependency types:

• Finish-to-Start (FS): Task B cannot start until Task A finishes. The most common type.
• Start-to-Start (SS): Task B cannot start until Task A starts. Useful for parallel work that must kick off together.
• Finish-to-Finish (FF): Task B cannot finish until Task A finishes. Common in testing and review workflows.
• Start-to-Finish (SF): Task B cannot finish until Task A starts. Rare, but useful for just-in-time scheduling.

You can add dependencies by dragging between tasks directly on the chart or by using the task detail panel.

Step 4: Set Up Baselines

Once your plan looks right, save a baseline. A baseline is a snapshot of your schedule at a specific point in time. As work progresses and dates shift, you can compare current dates against the baseline to see exactly where slippage has occurred.

Simple Gantt supports up to 10 baselines, so you can track how your plan evolves across major milestones or phase gates. Each baseline records start dates, end dates, and durations for every task.

Step 5: Activate Critical Path

Turn on critical path analysis to see which tasks directly determine your project end date. The critical path highlights the longest chain of dependent tasks — any delay to a task on this path pushes your entire project deadline.

Tasks not on the critical path have slack (also called float), meaning they can slip by a certain number of days without affecting the final deadline. Knowing which tasks have slack and which do not is essential for prioritizing work and allocating resources.

Step 6: Add Phases and Milestones

Organize your timeline with phases (groupings of related work) and milestones (key dates or deliverables). Phases give your chart visual structure, while milestones mark important checkpoints that stakeholders care about.

Getting the Most Out of Your Gantt Chart

Once you are set up, here are some tips for making your Gantt chart a real project management tool rather than just a pretty picture:

Use the Project Health Dashboard

Simple Gantt includes a project health dashboard with an automated risk score from 0 to 100. It runs 15+ validation rules against your project data, flagging issues like missing dependencies, unrealistic date ranges, and overloaded resources. Check it regularly to catch problems early.

Save Baselines at Key Moments

Do not just save one baseline and forget about it. Save a new baseline at each phase gate, after major re-planning sessions, or at the start of each quarter. Comparing baselines over time tells you whether your estimation accuracy is improving.

Keep Dependencies Clean

More dependencies does not mean better planning. Every dependency you add is a constraint on your schedule. Use the change history and audit trail to review dependency changes over time and ensure they still make sense.

Use Sprint Overlay

If your team works in sprints, enable the sprint overlay to see sprint boundaries on your Gantt chart. This helps you spot when planned work spans sprint boundaries, which often signals a task needs to be broken down.

Export and Share

Need to present to stakeholders who do not have Jira access? Use CSV or Excel export to share your project plan, or generate a shareable URL for view-only access.

When a Gantt Chart Makes the Difference

Gantt charts are not for every project. If you are running a continuous delivery team with no fixed deadlines, a Kanban board might serve you better. But when your project has:

• Hard deadlines that cannot slip
• Complex dependencies between teams or workstreams
• Stakeholders who need schedule visibility
• Multiple phases with sequential handoffs

Then a Gantt chart is the right tool. And having it inside Jira — where your team already works — means one less tool to manage and one less place for data to get out of sync.

Get Started

Simple Gantt is free to get started. Install it from the Atlassian Marketplace, create your first project in under five minutes, and see your Jira data on a real Gantt chart. No credit card, no complex setup, no data leaving your Jira instance.