How to Make a Gantt Chart in Power BI: A Step-by-Step Guide

A project plan can look organized in a task list while deadlines quietly drift, dependencies remain unclear, and overloaded team members go unnoticed. A regular Power BI chart often shows values well, yet it does not naturally display task duration across a calendar.

That creates a practical problem: you need one view that connects tasks, owners, dates, progress, and dependencies. Building it from scratch can feel technical, especially when your data needs reshaping before the visual works properly.

But here's the truth: you can create a useful Gantt chart in Power BI by preparing a simple task table, adding a compatible visual, mapping the right fields, and formatting the timeline. This guide walks you through each step.

How to Create a Gantt Chart in Power BI

To make a Gantt chart in Power BI, prepare task data with names, start dates, end dates or durations, and optional progress fields. Then add a Gantt visual from Microsoft AppSource, map each field, and format the timeline for your project.

Power BI does not include a standard Gantt chart among its default visual types. You typically add a Gantt visual from AppSource or use a custom visual already approved by your organization.

Here's the complete workflow:

1. Prepare a task table with one row per task.
2. Check date, duration, and progress values.
3. Open the Power BI report and add a Gantt visual.
4. Map task fields to the visual.
5. Configure hierarchy, milestones, dependencies, and colors.
6. Format the timeline for readability.
7. Test filters, sorting, and date behavior.
8. Publish and share the finished report.

Step 1: Prepare the Task Data

Start with a clean structure. Each row should represent one task, phase, milestone, or work package. Avoid combining several tasks in one row because the visual needs separate records to draw separate bars.

A practical task table may include these columns:

• Task name: The activity label shown on the chart.
• Task ID: A unique identifier for each activity.
• Parent task: The phase or summary group that contains the activity.
• Start date: The planned beginning of the task.
• End date: The planned completion date.
• Duration: The number of working or calendar days.
• Progress: Completion percentage, such as 0, 25, 50, or 100.
• Owner: The person or team responsible for delivery.
• Status: A label such as Planned, Active, Blocked, or Complete.
• Predecessor: The task that must finish before another task begins.

For example, a product launch plan might include “Confirm requirements,” “Build prototype,” “Run acceptance testing,” and “Release product.” Each activity needs its own dates.

Step 2: Check Date Types and Task Logic

Power BI reads dates according to their data type. A column that looks like a date may still be stored as text, which can prevent correct sorting and timeline behavior.

In Power Query, select each date column and set its type to Date or Date/Time. Then check for these common issues:

• End dates appearing before start dates.
• Blank dates on active tasks.
• Different date formats across rows.
• Duplicate task IDs.
• Progress values greater than 100 or below 0.
• Duration values that conflict with the start and end dates.

If a task starts on March 4 and ends on March 8, decide whether your plan counts five calendar days or four elapsed days. The answer affects duration calculations and should remain consistent across the report.

Step 3: Add a Gantt Visual

Open Power BI Desktop and load your project data. In the Visualizations pane, choose the option to import a visual from AppSource. Search for a Gantt visual and review its field requirements before adding it.

Different visuals support different features. Before choosing one, check whether it includes:

• Task hierarchy or parent-child grouping.
• Start and end date fields.
• Progress indicators.
• Milestone symbols.
• Dependency links.
• Color categories.
• Tooltips and drillthrough behavior.
• Conditional formatting.

The visual’s field names may differ. One visual may call a field “Task,” while another uses “Category” or “Task Name.” Focus on the role of each field rather than the label alone.

Step 4: Map the Required Fields

After adding the visual, drag your columns into the matching field wells. A typical configuration looks like this:

• Task: Task name.
• Start Date: Planned start date.
• End Date: Planned finish date.
• Legend or Group: Status, owner, or project phase.
• Parent: Parent task or phase.
• Progress: Completion percentage.
• Tooltip: Owner, budget, priority, risk, or notes.

If the visual asks for duration instead of an end date, create a duration measure or calculated column. For example, an elapsed calendar duration can use the difference between the end date and start date.

In DAX, a simple calculated column could look like this:

Duration Days = DATEDIFF(Tasks[Start Date], Tasks[End Date], DAY) + 1

The added one counts both the starting and ending calendar dates. Remove it if your planning method measures elapsed days between dates.

Step 5: Add Task Groups and Dependencies

A large project becomes easier to read when related activities sit under a phase. Add a parent field such as Design, Development, Testing, or Launch.

If your chosen visual supports dependencies, connect each task to its predecessor. For example:

• Prototype approval must finish before engineering begins.
• Engineering must finish before testing starts.
• Testing must finish before release preparation begins.

Dependency relationships make delays easier to interpret. If testing moves by three days, the release date may also move unless you have planned parallel work.

Some custom visuals require a predecessor ID, while others need a relationship field. Read the visual’s field instructions and use unique task IDs to avoid ambiguous links.

Step 6: Configure Milestones and Progress

Milestones mark important points with little or no duration. Examples include a contract approval, design sign-off, production release, or regulatory review.

If your visual supports milestones, use a milestone date and label. If it does not, create a one-day task with a distinctive status or color. Keep milestone labels short so the timeline remains readable.

For progress, use a percentage measure rather than a text label. A value of 75 means 75 percent complete in some visuals, while others expect 0.75. Confirm the visual’s requirement before applying conditional formatting.

Step 7: Format the Gantt Chart

Formatting determines whether your report helps someone make a decision or simply displays colored bars. Start with the timeline scale, then improve labels and colors.

• Use weeks for short projects and months for longer programs.
• Choose a contrasting color for blocked work.
• Use one consistent color for completed tasks.
• Keep phase colors distinct from status colors.
• Show data labels only when they do not overlap.
• Place essential details in tooltips instead of crowded labels.
• Use a clear title that includes the project or reporting period.

For example, a 12-week software release plan may need weekly intervals, while a two-year construction program may work better with monthly intervals.

Step 8: Test Filters and Publish

Add slicers for project, owner, phase, status, and reporting period. Then test how the chart responds when you select each option.

Check whether a status filter changes both the bars and the summary measures. Confirm that dates remain chronological and that completed tasks do not disappear unexpectedly.

Finally, publish the report to your Power BI workspace. Verify permissions, refresh behavior, mobile layout, and export options before sharing it with your team.

What a Power BI Gantt Chart Should Show

A useful chart answers several questions quickly: What work is planned? When does it happen? Who owns it? How much is complete? Which tasks may delay the outcome?

The core visual usually contains horizontal bars across a date axis. Bar length represents task duration, while position shows when work begins and ends.

Keep the chart focused. If color represents status, use tooltips for owner and priority. If color represents owner, use a status slicer to identify delays.

Here's why: asking one visual to communicate every attribute at once usually creates noise. A clean chart supports faster decisions.

How to Build Useful Measures for the Timeline

Measures can turn a static schedule into a management view. They help you compare planned dates, actual progress, and overdue work.

Completion Percentage

If each task has a completion value, you can calculate average completion across selected tasks. A simple weighted measure can use task duration, so a long activity contributes more than a short activity.

For example, a project with one 20-day task at 50 percent and one 2-day task at 100 percent should not necessarily report 75 percent completion. Duration-weighted progress may provide a more realistic view.

Overdue Task Count

Create a measure that counts tasks where the planned end date has passed and progress remains below 100 percent.

This lets you place a card beside the Gantt chart showing the number of overdue activities. Selecting a phase or owner can then reveal where delays are concentrated.

Schedule Variance

If you have baseline dates and current forecast dates, calculate the difference between them. A positive variance may indicate a later forecast, while a negative value may indicate an earlier finish.

For example, a task originally planned to finish on June 10 but now forecast for June 14 has a four-day delay. Displaying this beside the task bar gives context without adding another crowded label.

Critical Task Indicator

You can add a field that identifies activities with little schedule flexibility. Use a distinct color or icon for these tasks.

Suppose “Security review” has only one day of flexibility before product release. Highlighting it helps the project lead prioritize attention, even if another task has a longer duration.

Common Design Mistakes to Avoid

The most common issue is treating a Gantt chart as a decorative timeline. A project view should help you detect risk, clarify responsibility, or make a scheduling decision.

Using Text Instead of Real Dates

Text such as “March 2026” may look readable, but Power BI cannot always sort it chronologically. Use a proper date column and create a separate display label when needed.

Mixing Summary Tasks and Detail Tasks

A phase row and its child activities may overlap in confusing ways if the visual does not understand the hierarchy. Decide whether the phase bar represents the full span of its children or serves only as a heading.

Showing Too Many Colors

Ten owners, eight statuses, and six priorities can produce an unreadable legend. Choose one primary color dimension, then use filters and tooltips for the rest.

Ignoring Time Zones and Date Boundaries

Date and time values can shift when refresh processes use different time zones. This matters for tasks that start near midnight or reports shared across regions.

Skipping Mobile Testing

A wide desktop chart may become difficult to use on a phone. Create a mobile layout with summary cards, filters, and a narrower time range when field teams need access away from a desk.

Practical Ways to Improve Project Reporting

A Gantt chart becomes more valuable when you pair it with a few supporting visuals. Place a task-status summary, overdue count, owner workload view, and risk indicator near the timeline.

For example, a project manager might select “Testing” from a phase slicer. The Gantt chart then narrows to testing activities, the overdue card updates, and the owner view shows who handles the delayed work.

The best part? You can keep the chart focused while still giving decision-makers access to detail through tooltips and drillthrough pages.

Use a consistent reporting rhythm. During a weekly review, compare the current forecast with the previous refresh. Look for tasks that moved, progress that stalled, and dependencies that changed.

Let me explain the value of this approach: the timeline shows when work happens, while the surrounding measures explain why attention is needed.

Project Planning Solution: ONES.com

Value Proposition

ONES.com combines project management and knowledge management in one platform powered by ONES Assistant. ONES Project supports Jira-compatible workflows, reporting, sprint planning, custom fields, and automation without requiring a separate project workspace for every planning activity.

It can serve as a Jira alternative for teams that need structured planning, flexible deployment, and a connected place for project knowledge. ONES Project and ONES Wiki are sold separately.

Core Capabilities

• Scattered project information → Unified project workspace → Keep tasks, schedules, owners, and status details connected within a single project environment.
• Limited reporting views → Built-in reporting → Use reporting capabilities to monitor progress, workload, and schedule health without assembling every view manually.
• Rigid planning fields → Custom workflows and fields → Adapt task states, approval steps, and project attributes to match your operating process.
• Sprint planning gaps → Sprint management → Organize iterative work into sprints while keeping task relationships and priorities visible.
• Repetitive updates → Automation → Automate routine transitions and actions so common project events require less manual handling.
• Migration concerns → Jira-compatible workflows → Give teams familiar workflow concepts when they are evaluating a Jira alternative.
• Plugin dependency → Native capabilities → Reduce reliance on multiple add-ons by using built-in project management functions.
• Deployment restrictions → Four deployment options → Choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment according to operational and security requirements.
• Budget pressure during evaluation → Free plan for 30 seats → Test the platform with up to 30 seats before deciding whether it fits larger adoption needs.
• Inconsistent platform behavior → Feature parity → Use the same full feature set across the cloud and self-hosted versions.

Application Scenarios

Software release planning: A development team can organize epics, sprints, testing activities, approvals, and release tasks in ONES Project. Custom fields can identify risk, release train, or service area, while reports show progress across workstreams.

Regulated or restricted environments: A team that cannot use a public cloud deployment can evaluate the On-Premise, Private Cloud, or Air-gapped options. The same feature parity helps reduce the need to redesign workflows for a different deployment model.

Project knowledge management: A team can pair ONES Project with ONES Wiki to connect delivery work with requirements, decisions, procedures, and meeting knowledge. This is useful when schedule decisions need context beyond task fields.

Common Challenges and Practical Solutions

The Visual Does Not Display Any Bars

Problem: The visual may lack a valid start date, end date, or task field.

Solution: Check that each required field is mapped and that date columns use a date type. Test with three simple tasks before adding the full plan.

Tasks Appear in the Wrong Order

Problem: Power BI may sort task labels alphabetically instead of by start date or sequence.

Solution: Add a numeric sort-order column and use “Sort by column” in the model. Keep task IDs separate from display names.

Progress Bars Look Incorrect

Problem: The visual may expect a decimal between 0 and 1, while your measure uses percentages between 0 and 100.

Solution: Check the visual settings and convert the value when necessary. Format the result as a percentage only after confirming the underlying scale.

Dependencies Do Not Connect

Problem: Predecessor values may not match task IDs exactly.

Solution: Use unique IDs, remove accidental spaces, and verify that each predecessor exists. Avoid using task names as relationship keys when names can repeat.

The Chart Becomes Too Crowded

Problem: Too many tasks, labels, colors, and date intervals compete for space.

Solution: Add hierarchy, filters, and drillthrough pages. Start with a phase-level view, then let viewers expand or filter into task detail.

FAQs

Can Power BI create a Gantt chart without a custom visual?

Power BI does not provide a standard Gantt chart among its primary built-in visuals. You can approximate one with a stacked bar chart, but that approach usually requires extra measures and careful formatting. A dedicated Gantt visual is generally easier for task duration, progress, milestones, and dependencies. Check your organization’s approval rules before importing a visual from AppSource.

What columns do I need for a Power BI Gantt chart?

The basic setup needs a task name, start date, and end date. You can add task ID, parent phase, progress, owner, status, and predecessor fields for richer project tracking. Keep one task per row and use consistent date types. If the visual uses duration instead of an end date, include a reliable duration value calculated from your planning rules.

How do I show task progress in the chart?

Map a numeric progress field to the visual’s progress well, if available. Confirm whether the visual expects values from 0 to 1 or 0 to 100. A value of 0.75 may represent 75 percent in one visual, while another expects 75. Add conditional formatting so completed, active, and delayed work can be distinguished without relying on labels alone.

Can I show dependencies between tasks?

Some Gantt visuals support dependency lines through predecessor IDs or relationship fields. Give every task a unique ID, then connect each activity to the task that must happen first. For example, testing may depend on development completion. If your chosen visual lacks dependency support, add predecessor details to tooltips or create a companion relationship view.

How can I make the chart easier to read?

Limit the number of colors, use a suitable time scale, group tasks into phases, and place secondary details in tooltips. A short project may need weekly intervals, while a long program may need monthly intervals. Add slicers for owner, status, phase, or project. Keep the first view at summary level, then let viewers filter into detail.

Is a Gantt chart suitable for agile projects?

It can help with release planning, sprint milestones, dependencies, and cross-team coordination. It should complement sprint boards rather than replace daily task management. Use the timeline for broader delivery commitments, then use sprint views for active work, changing priorities, and team-level execution.

Conclusion

To build a Gantt chart in Power BI, prepare one row per task, use valid start and end dates, add a compatible visual, map the required fields, and test the report with realistic filters.

Start with the smallest useful view: task, start date, end date, status, and progress. Then add phases, milestones, dependencies, owners, and schedule measures as your reporting needs become clearer.

But here's the truth: a timeline alone cannot fix unclear ownership or inconsistent planning. It becomes powerful when your task structure, dates, progress rules, and review habits work together.

If your team needs a broader project management environment beyond Power BI reporting, ONES.com can connect structured project workflows, reporting, automation, and knowledge management in a platform that supports cloud and self-hosted deployment.