Jira dashboard Gantt chart

Schedules live in one tool, execution lives in another, and by the time leadership sees the timeline it's a screenshot in a slide deck. Putting the Gantt view directly on a Jira dashboard fixes that: Schedule, dependencies, and rolled-up status show up where teams already check blockers and burndowns, drawn from the same underlying Jira data.

What is a dashboard Gantt view in Jira?

A dashboard Gantt view is a timeline of Jira work — issues, epics, initiatives, releases — rendered alongside the rest of a Jira dashboard. Instead of leaving Jira to see a schedule, the timeline sits next to the issue lists, charts, and filters teams already rely on.

For organizations using Gantt Charts for Structure PPM, the dashboard view is delivered through a first-party gadget that renders a configured Structure timeline on the dashboard itself. Stakeholders open one Jira dashboard and see schedule, dependencies, and progress without switching to a separate planning tool.

The result is a single place where execution data and schedule data meet — useful for status reviews, steering committees, and any meeting where someone asks, "What's the plan and where are we on it?"

Benefits of putting a Gantt view on the dashboard

• One source of truth. Schedule, status, and Jira issues live together, so the timeline can't drift from reality.

• Less context switching. Stakeholders don't open a second tool to see the plan — the timeline is one click from their other Jira widgets.

• Faster status conversations. Reviewers move from a rolled-up timeline to the underlying epics and stories without leaving the dashboard.

• Audience-specific dashboards. Program, portfolio, and release teams each configure their own dashboard and pull the Gantt view that matches it.

How to set one up

Start by deciding who the dashboard serves. A program manager's dashboard needs detail down to the sprint and dependency level. A portfolio dashboard for executives needs the same data rolled up to initiatives and milestones. Build the underlying Structure hierarchy first, then add the gadget so the timeline reflects the same hierarchy as the rest of the dashboard.

When you add the gadget, configure four things to match the audience: Which Structure to load, the hierarchy depth to display, the starting date (Project Start, Today, or a Custom date), and the zoom level (Days, Weeks, Months, Quarters, or Years). Toggle on the WBS view if reviewers need an issue list alongside the chart — the WBS view typically supports Key and Summary columns. If the underlying chart has baselines, surface them in the gadget so leadership can see slippage against the original plan.

Pair the gadget with related Jira dashboard widgets — issue lists filtered by the same Structure, sprint progress widgets, custom charts pulling Structure data — so the dashboard tells one coherent story instead of three disconnected ones.

Managing dashboard timelines with Gantt Charts for Structure PPM

Gantt Charts for Structure PPM is the most flexible Gantt solution for Jira. It runs on top of Structure PPM, so every timeline draws from a configurable hierarchy that teams shape to match how they plan — Agile, Waterfall, or hybrid.

That hierarchy is what makes a dashboard-friendly Gantt view possible. Collapse the Structure to show only parent initiatives for an executive dashboard. Expand it for a program manager who needs sprint-level visibility. Build multiple Structures — one per portfolio, program, or release — and surface the timeline that matches each dashboard's audience.

Gadget availability

Where the first-party gadget is available depends on the platform and edition:

• Data Center. The gadget is fully available. Add it to any Jira dashboard, point it at an existing Structure and chart, and it renders in place.

• Cloud (standalone Gantt extension). The gadget is available when the standalone Gantt extension is installed alongside Structure.

• Cloud (Structure PPM Advanced edition). When Gantt is bundled as part of Structure PPM Advanced on Cloud, the dashboard gadget is currently unavailable. For dashboard reporting on Structure data in this scenario, Tempo points users to Custom Charts for Jira, which supports Structure-sourced reporting on Jira dashboards and in Confluence.

What the gadget does (and does not) do

The gadget is a read-only view tuned for reporting and review. It is configurable on the dimensions reviewers care about: Which Structure to load, hierarchy depth, starting date (Project Start, Today, or Custom), and zoom level (Days, Weeks, Months, Quarters, Years). The WBS toggle adds an issue list beside the chart, generally with Key and Summary columns. Baselines configured on the underlying chart can be displayed in the gadget so reviewers can monitor slippage at a glance.

What the gadget does not do is substitute for the main Structure board. Drag-and-drop rescheduling, creating dependencies, and other edits stay in the full Gantt view. The gadget is for the audience that needs to see the plan, not change it.

For Cloud Advanced customers without the standalone extension, Custom Charts fills the dashboard reporting gap — pie, bar, stacked bar, line, table, and tile charts can all pull from a Structure hierarchy and live alongside other widgets on the same Jira dashboard.