Gantt configuration

An editable schedule where the built-in Gantt is a picture. Drag a bar to move it, drag its edge to resize, draw a dependency between two issues, and see the Critical path through the plan. Baselines record what you promised so Drift can show what actually happened. There is a per-project chart on the Gantt tab and a Gantt — all projects view across everything you can see.

Every change is an ordinary issue edit underneath — the same rules, the same history entry, the same notifications — so a drag can never be a way to move a date without leaving a trail.

On RedminePRO Cloud

Availability

Business and above.

Turn it on

Nothing to turn on. This replaces the built-in Gantt tab in every project, so it appears wherever that tab already did. The built-in chart stays reachable from a link at the foot of the page.

There is deliberately no module of its own: gating a tab every project already had behind an opt-in would make it vanish from existing projects on upgrade.

Permissions

Administration → Roles and permissions:

Editing a bar needs the ordinary issue permissions — a drag is an issue edit, so it obeys exactly what that person could do on the issue form. Reading a baseline rides on View Gantt; only writing one needs the second permission, so a viewer can see the plan-against-actual story without being able to rewrite the record of it.

On upgrade, View Gantt is granted automatically to every role that could already see issues, so nothing disappears.

Settings

Administration → Plugins → RedminePRO Gantt:

Using it

1. Open a project's Gantt tab, or Gantt — all projects from the top menu.
2. Zoom between Day, Week, Month and Quarter. Today jumps back to now.
3. Colour by Status, Priority, Assignee or Project.
4. Drag a bar to move the dates; drag an end to change the duration. Saving one issue can reschedule what follows it and roll dates into a parent — the chart tells you what else moved.
5. Draw a dependency between two issues with Link. Whether an edge is legal depends on cycle and cross-project rules, so it is confirmed by the server before it is drawn.
6. Critical path marks the chain with no slack.
7. Save baseline records the current dates under a name. Choose it afterwards to show Drift beside each row.
8. Undo reverses your last change — as a real edit, so it journals and notifies like any other. One drag and one undo leave two history entries.
9. Export produces a PNG image or CSV (table).

Issues with no dates are listed rather than hidden, so you can schedule them instead of losing them.

Troubleshooting

Progress will not change by dragging. Administration → Settings → Issue tracking → Calculate the issue done ratio with is set to use the status. In that mode the value is derived from the status and a drag is refused up front, rather than accepted and then ignored on the next load.

A save was refused and the bar sprang back. Someone else changed that issue after your chart was drawn. The current row is sent back so the chart redraws rather than overwriting whoever saved first.

A dependency I drew did not appear. The server refused it — a cycle, or a cross-project rule. The edge is confirmed before it is drawn precisely so an invalid dependency never flashes onto the chart.

Something moved that I did not touch. Saving one issue reschedules what follows it and can roll dates into a parent. That is Redmine's own scheduling, observed and reported rather than reimplemented. Followers you cannot see still move; you are simply not told about those.

Not everything is on the chart. A single load is capped, and the chart says when it was truncated. Narrow the date window or the filters.

I want the old chart. Follow Switch to the classic Gantt at the foot of the page.