How to Build a Gantt Chart in Jira: A Step-by-Step Guide
Need a clearer project schedule? Learn how to build gantt in Jira, link tasks, and manage dependencies. Read now to plan with confidence.
A Gantt chart can make a Jira project’s dates, tasks, and dependencies easier to understand. But when you open Jira, it may be unclear whether the timeline you need is already available or requires extra setup.
That uncertainty can lead to missed handoffs, crowded boards, and plans that look complete but hide schedule risks. The good news: you can start with Jira’s built-in timeline, then add a Marketplace app if your project needs more control. Here’s how to build a useful Gantt-style view, connect tasks, and keep the schedule trustworthy as work changes.
How to Build a Gantt Chart in Jira
Start by organizing your work into issues, adding start and due dates, and connecting dependent tasks. Then choose a Jira timeline or a Gantt app that fits the level of planning your team needs.

1. Choose the Jira project and timeline option
First, decide whether you need a simple project timeline or a more detailed Gantt chart. Jira’s built-in timeline can suit straightforward planning, while larger plans may need advanced planning features or a Marketplace app.
Availability and navigation vary by Jira edition, project type, and permissions. Check the features enabled in your Jira site before planning around a specific view.
2. Break the project into manageable issues
Create an issue for each meaningful task, then group related work under parent issues or epics. For example, a website launch might include “Prepare product pages” as a parent item, with separate issues for copy, design, and review.
Keep tasks small enough to estimate and assign. A single issue called “Build the website” is difficult to schedule because it hides the work and handoffs underneath it.
3. Add start and due dates
Enter a planned start date and a due date for each issue that needs to appear on the timeline. These dates give Jira the information it needs to display task durations.
If the date fields aren’t visible, ask a Jira administrator whether they’re available on the project’s issue screens. Check a few representative issues after adding dates; missing or inconsistent dates can make a timeline look incomplete.
4. Set task ownership and status
Assign each issue to the person or team responsible for moving it forward. Keep statuses meaningful, such as “To Do,” “In Progress,” and “Done,” so the timeline reflects actual progress.
For example, a review task shouldn’t appear complete just because the preceding design issue is finished. Give the review its own owner, dates, and status.
5. Link tasks that depend on one another
Add issue links to show relationships such as “blocks” or “is blocked by.” If development can’t start until the design is approved, connect those issues so the handoff is visible.
Dependencies help you spot schedule risks that dates alone can conceal. A task may appear to fit within the timeline, yet still be impossible to start until another issue is complete.
6. Open and configure the timeline view
Open the project’s timeline or the planning view available to your team. Choose the relevant issues, group them by parent item or another useful category, and adjust the date range so the full project is visible.
Use a level of detail that helps people make decisions. A leadership review may need epics and milestones, while a delivery team may need individual tasks and dependencies.
7. Review the schedule, then keep it current
Check that every key task has an owner, dates, and the right links. Look for overlapping work, gaps between dependent tasks, and deadlines that leave no room for review or testing.
Set a regular update rhythm, such as a short review every Monday. When a task slips, revise its dates and affected dependencies instead of leaving an outdated plan in place.
What a Jira Gantt View Can Show
A Gantt-style view places work along a calendar, so you can see when tasks begin, how long they are expected to take, and how they relate to each other. Bars represent planned work, while links can show which tasks must happen first.
For example, a release plan might show development from June 3 to June 14, testing from June 17 to June 21, and launch preparation from June 24 to June 26. If testing depends on completed development, the sequence is clear at a glance.
But here's the truth: the chart is only as reliable as the dates, ownership, and issue links behind it. A polished timeline with stale dates can create more confusion than a simple task list.
Built-In Timeline or Gantt App?
Jira’s built-in timeline can be a practical starting point when you need to view work over time without adding another app. It may be enough for a small team tracking epics, target dates, and basic dependencies.
A dedicated Gantt app may be a better fit when you need more detailed scheduling, critical-path views, resource planning, or richer controls. For example, a construction project with several teams and tightly sequenced handoffs may outgrow a basic timeline.
Here’s why: the right option depends on the decisions your team needs to make. List those needs first, then compare them with the features available in your Jira edition and any app you’re considering.
How to Keep the Timeline Useful
Make the timeline part of your project routine instead of treating it as a one-time setup. Ask owners to update their issue status and dates before planning meetings, then use the view to discuss changes and blockers.
Keep dates realistic. If a task has five days of work and a one-day review, schedule both pieces instead of assigning one optimistic deadline to the entire activity.
You might be wondering: how much detail should you include? Add enough tasks to reveal important handoffs and risks, but avoid representing every small action as a separate timeline item. A plan with hundreds of tiny bars can be difficult to scan.
Common Gantt Chart Mistakes in Jira
One frequent mistake is adding due dates without start dates. The result may show deadlines but fail to communicate how long work is expected to take. Agree on which date fields your team will maintain, then apply that rule consistently.
Another issue is using parent tasks without clear owners or child issues. A parent item may show a broad period, but the team still needs specific tasks to understand who is doing what. For instance, “Prepare launch” becomes more actionable when it includes separate work for testing, communications, and approvals.
Finally, avoid treating every dependency as a hard blocker. Some work can proceed in parallel while teams resolve open questions. Link only genuine sequencing requirements, or the chart may suggest a slower schedule than the team actually needs.
ONES.com Solution: A Project Planning Option

Value Proposition
ONES.com combines project management and knowledge management in one platform, with ONES Project for project work and ONES Wiki for knowledge management. They are sold separately, so you can choose the product that fits your team’s needs.
If you’re considering a Jira alternative, ONES Project offers project planning features such as custom workflows, sprint management, automation, and built-in reporting. It supports Jira-compatible workflows and can be deployed in cloud or self-hosted environments.
Core Capabilities
- Planning feels scattered: ONES Project brings project work into a dedicated project management environment, helping teams keep tasks and schedules connected.
- Workflows don’t match team processes: Custom workflows let teams define steps that reflect how their work moves, so issue statuses can better represent real progress.
- Fields don’t capture enough planning detail: Custom fields give teams ways to track relevant information alongside tasks, helping clarify scope and ownership.
- Sprint work is hard to coordinate: Sprint management supports teams organizing work into planned development cycles, making progress easier to review.
- Repeated actions take time: Automation can handle routine workflow actions, reducing manual updates for recurring project processes.
- Progress is difficult to inspect: Built-in reporting gives teams ways to review project activity and status without relying entirely on separate add-ons.
- Jira workflows are already familiar: Jira-compatible workflows can make it easier for teams to carry established process patterns into a Jira alternative.
- Hosting requirements differ across teams: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Its self-hosted version has full feature parity with the cloud version.
Application Scenarios
A product team could use ONES Project to organize releases into epics, sprint work, and linked tasks. Custom workflows can represent design review and testing steps, while reporting helps the team inspect progress before release meetings.
An organization with strict network restrictions could consider an Air-gapped or other self-hosted deployment. A smaller team assessing the platform can also start with the free plan, which supports up to 30 seats.
Teams that also need a knowledge management product can evaluate ONES Wiki separately. This keeps project planning and knowledge management as distinct product choices within the broader ONES.com platform.
Common Challenges
- Dates are missing or inconsistent. Solution: Agree on which start and due date fields to use, make them available on relevant issue screens, and check dates during regular planning reviews.
- Dependencies are unclear. Solution: Link tasks only when one genuinely needs another to finish first. Add a short explanation to the issue so the reason for the relationship is easy to understand.
- The timeline contains too much detail. Solution: Use parent issues for high-level reviews and show individual tasks when the audience needs delivery detail. Save different views for different planning conversations where possible.
- Dates change but the chart doesn’t. Solution: Make timeline updates part of your team’s regular status routine. When a delay affects dependent work, review those dates together rather than shifting only one task.
FAQs
Does Jira have a built-in Gantt chart?
Jira offers timeline and planning views, but the features available depend on your Jira edition, project type, and configuration. A built-in timeline may meet basic scheduling needs, while advanced planning or a Marketplace app may be necessary for more detailed Gantt capabilities. Check the views enabled in your own Jira site before choosing an approach.

How do I show task duration in a Jira timeline?
Add a start date and a due date to each issue you want to schedule. The gap between those dates represents the planned duration in the timeline. If one or both fields aren’t visible, ask a Jira administrator to check the project’s issue screens and field configuration. Keep the dates updated as work changes.
Can I show dependencies in a Jira Gantt chart?
Many Jira planning views and Gantt apps can display issue relationships, but the available dependency features vary. In Jira, link related issues with relationships such as “blocks” and “is blocked by,” then check whether your chosen view displays them. For example, connect design approval to development if development cannot begin before approval.
When should I use a Jira Gantt app instead of a built-in timeline?
Try the built-in timeline when your team needs a straightforward view of tasks, dates, and basic planning. Consider a Gantt app if you need capabilities such as critical-path analysis, detailed resource planning, or more scheduling controls. Compare the requirements of a real project before adopting an app, since extra features also add setup and maintenance.
Conclusion
To build a useful Gantt-style plan in Jira, organize work into clear issues, add realistic start and due dates, link genuine dependencies, and review the timeline regularly. Choose a built-in view for simpler planning or explore a dedicated app when your team needs more control.
A timeline can’t fix unclear ownership or stale schedules on its own. But with a consistent update routine, it can reveal handoffs and delays early, giving you a clearer way to keep project work moving.