Pulse Gantt: a free Gantt chart for Power BI

• Task, Group by, Task ID and Predecessors are categories. Power BI makes one row for each different combination of their values, plus any text or date field in Columns. So a task with two rows in your table, which differ in one of those fields, becomes two rows in the chart.
• Start, End, Progress, Baseline start, Baseline end, Critical flag and Tooltips are values. Power BI aggregates them for each row, so each one needs the right aggregation (the arrow next to the field in the well). Microsoft's Work with aggregates page lists earliest, latest, first and last as the options for dates, and Sum as the default for numbers.
• The rows arrive sorted by Start, earliest first (the visual asks Power BI for that sort). A blank sorts as the lowest value, so rows with no Start come first. Groups appear in the order of their first task.
• The visual reads up to 10,000 rows.

Task

• What it means: the label for each row. The only required field: with Task empty, the visual shows its landing page.
• Column type: any. Usually text.
• Aggregation: none. It's a category.
• Good example: a task name column, such as Task or Activity.
• Values: shown as text, with the column's format.
• If it's empty: for one row, the row is labelled with its position, starting at 1.
• Tips and mistakes: two tasks with the same name stay separate when another category tells them apart (a Group by or a Task ID). Selecting a row, by click, Enter or Space, selects that task for cross-filtering; Ctrl-click adds more.

Group by

• What it means: up to three levels that group the tasks, outermost first, such as phase and then workstream.
• Column type: any. Usually text.
• Aggregation: none. It's a category.
• Good example: Phase, or Stage then Crew.
• Values: each different value becomes a group row with an arrow to collapse it. The group row shows how many tasks are under it and their progress, weighted by each task's length in days.
• If it's empty: for one row, the row goes in a group called (Blank).
• Tips and mistakes: each group row has a roll-up bar from its tasks' earliest start to their latest end; collapsed, the group also keeps its milestones on that bar. Connector lines to hidden tasks attach to the group's row. Where Power BI turns interactions off (on a dashboard tile, for example), groups can't be collapsed.

Start

• What it means: the day the task starts.
• Column type: Date (or Date/Time; the time is ignored).
• Aggregation: Earliest. With one row per task, Earliest and Latest give the same date; Earliest keeps the task's first date if it has several rows.
• Good example: Start with the Date data type.
• Values: the visual takes the calendar date of each value. A bar covers its Start day to its End day, both in full.
• If it's empty: with an End, the task is drawn as a one-day bar on its End date. With neither, the row has no bar.
• Tips and mistakes: check the column's data type is Date. A number in Start is read as milliseconds since 1 January 1970, so an Excel serial date such as 46293 puts the bar in January 1970; Sum is Power BI's default for a number column, while a Date column gets date options (earliest, latest, first and last) instead. Count gives a number too, with the same result. Text dates are read with the browser's date reader, which can land a day early west of UTC, so set the type to Date in Power Query instead.

End

• What it means: the day the task ends, counted in full.
• Column type: Date (or Date/Time; the time is ignored).
• Aggregation: Latest, so a task with several rows ends on its last date.
• Good example: End or Finish date.
• Values: as for Start. An End before its Start draws a sliver at the Start.
• If it's empty: for a row with a Start, the task is a milestone: a diamond on its Start day.
• Tips and mistakes: to make a milestone, leave End blank. Don't put the same date in Start and End: that's a one-day task, not a milestone.

Progress

• What it means: how complete the task is. It fills the bar and the % column.
• Column type: a number.
• Aggregation: Sum when each task has one row. If a task can have several rows, use Average or Maximum: see the mistake below.
• Good example: Progress from 0 to 1, or % complete from 0 to 100.
• Values: each value is read on its own. Above 1, it's divided by 100 (so 0–100 works); from 0 to 1, it's taken as it is. Anything below 0 counts as 0 and anything above 100% as 100%. At 100% the task counts as done: green with a ✓, unless it's on the critical path, which keeps the critical colour and icon.
• If it's empty: for one row, the bar has no fill and the % column shows a dash.
• Tips and mistakes: on a 0–100 column, a value of 1 or less is misread: 1 (meaning 1%) shows as 100% and done, and 0.5 as 50%. Convert the column to 0–1 if it can hold such small values. With Sum, two rows of 0.6 for one task add up to 1.2, which is then read as 1.2%.

Task ID

• What it means: the identifier that Predecessors lists point at.
• Column type: text or a number.
• Aggregation: none. It's a category.
• Good example: Task ID with values such as T1, T2, or Activity ID with A1, A2.
• Values: compared as text, exactly: T6 doesn't match t6 or T 6. A number 5 matches the text 5.
• If it's empty: for one row, that row's ID becomes its position in the sorted list, counting from 0. With the whole field empty, every row gets its position as its ID.
• Tips and mistakes: Task ID does nothing on its own; it's what makes Predecessors work. Keep IDs unique: if two rows share one, links go to the first in Start order.

Predecessors

• What it means: the tasks this task waits for. Each one draws a connector line from the end of that task to the start of this one, and links the two in the float engine.
• Column type: text (a number works for a single ID).
• Aggregation: none. It's a category.
• Good example: Predecessors with values such as T6, T7; T8.
• Values: IDs separated by commas, semicolons or vertical bars (, ; |), with or without spaces around them. T6, T7; T8 and T6;T7|T8 both mean T6, T7 and T8. Each ID must match a Task ID exactly. A task listing itself is ignored, and an ID that matches no task is dropped from the lines and the float, though the tooltip's After line still lists it.
• If it's empty: for one row, the task waits for nothing.
• Tips and mistakes: bind Task ID too. Without it, the IDs are row positions from 0, so T3 matches nothing and no lines are drawn; plain numbers are worse, because 3 would link to the fourth row. Every link is finish-to-start with no lag: a link type or lag written into the ID, as in 3FS+2 days, makes it an unknown ID that's dropped. A loop (T12 waits for T13, which waits for T12) is a cycle: see The float engine.

Baseline start

• What it means: where the task's original plan started, for the grey baseline line.
• Column type: Date.
• Aggregation: Earliest, as for Start.
• Good example: Baseline start or Planned start.
• Values: as for Start.
• If it's empty: for one row, the baseline line uses Baseline end for both ends. With both empty, the row has no baseline.
• Tips and mistakes: for a milestone, Baseline start is its planned date: when it moved, the old date shows as a hollow diamond tied to the new one by a dotted line, and the slip is the Start minus the Baseline start.

Baseline end

• What it means: where the task's original plan ended. The slip is the task's End minus its Baseline end, in calendar days (weekends included). It drives the slip badges, the Slip column and the header's verdict.
• Column type: Date.
• Aggregation: Latest, as for End.
• Good example: Baseline end or Planned finish.
• Values: as for End. A positive slip is late (▲ +3d); a negative one is early (▼ -2d).
• If it's empty: for one row, Baseline start is used in its place. With both empty, there's no slip.
• Tips and mistakes: slip badges show only for late tasks, and only where there's room to the right of the bar; they're left out in high contrast, where the Slip column still gives the number.

Critical flag

• What it means: your own critical path, for example a flag exported from Microsoft Project, in place of the one the visual computes.
• Column type: text (Yes/No, True/False) or a number.
• Aggregation: First for text, Maximum for a number.
• Good example: a Critical column with Yes or No.
• Values: critical when the value is true, a number above 0, or the text true, yes, y or 1 in any case. Anything else, including a blank, is not critical.
• If it's empty: for one row, that task isn't critical. As soon as any field is in this well, it decides for every task, and the computed critical path is off.
• Tips and mistakes: with the flag bound, Critical within in the format pane has no effect.

Columns

• What it means: up to three extra columns beside the task names, such as owner or status.
• Column type: any. Text and dates are shown as they are; a number is aggregated like a value.
• Aggregation: none for text and dates (they're categories); Sum or another aggregation for numbers.
• Good example: Owner.
• Values: shown with the column's format, in a narrow column that cuts long text short. The column heading is the field's name. Text and date fields come before number fields, whatever their order in the well.
• If it's empty: for one row, the cell is blank.
• Tips and mistakes: a text or date field here is a category, so a task with two owners becomes two rows. Use a single-valued column, or put the field in Tooltips instead.
• When the list is narrow: the list keeps the task names at least 80 px wide and leaves out the columns that don't fit, keeping Slip and % first, then your Columns in order, then the start and end dates. Widen the task list (format pane, Task list, Width) to bring them back.

Tooltips

• What it means: up to five more fields for the tooltip.
• Column type: any.
• Aggregation: any; the tooltip shows the result with the field's name, such as Sum of Budget.
• Good example: Budget, Owner.
• Values: shown under the visual's own tooltip lines: the task and its group path, Schedule, Progress, Baseline, Slip, Float (and "on the critical path"), and After (the predecessors).
• If it's empty: for one row, that line is left out.
• Tips and mistakes: tooltips work even where Power BI turns interactions off.

With dependencies bound, the visual works out each task's float: the working days it can slip before it pushes a successor, chained through to the project end. For a task with successors, float is the smallest of (working days between its end and the successor's start, plus that successor's float). A task with no successors floats against the project end, which is the latest End (or a milestone's Start) in the data. Working days are Monday to Friday; there are no holidays, and the days counted are those strictly between the two dates.

• Tasks with float at or under Critical within (format pane, Critical path; 0 by default, up to 30) are the critical path: drawn in the critical colour, with the » icon, and a thicker line in that colour between two critical tasks.
• Without dependencies, every task floats against the project end, so only the tasks finishing within the threshold of the last day are critical.
• A cycle (tasks that wait for each other) has no order, so float can't be worked out through it. The visual finds it and leaves the tasks on it, and every task after them, out of the float and the critical path: their tooltips have no Float line, and they're never critical. Their bars and lines are still drawn. It never guesses which link is wrong; fix the data.
• A Critical flag field replaces all of this for every task.

The header reads the result: Finish (the project end), the slip against baseline (the worst slip on the critical path), and, when the project is late, the driver: the earliest-starting task that slipped at least as much. When no critical task has a baseline, the slip compares the project end with the latest baseline date in the data.

In Windows high contrast, the visual uses only the two colours Power BI gives it, drops the weekend shading and slip badges, and keeps every status readable from its icon and text. The animation never plays for anyone whose device asks for reduced motion.