Skip to content

Gantt Pro for Project

An interactive Gantt for project tasks with the critical path computed in Python.

The short answer

Gantt Pro for Project draws project tasks on an interactive timeline and works out the critical path and each task's slack on the server, in Python. It suits project managers on Odoo 18 or 19, Community or Enterprise, who need to know which tasks set the finish date and which have room. Reports and automated actions can read the result too.

Request this module

Last updated

What it is for

A project plan is a list of things that have to happen, and a list gives you no way to tell which of them you can be late on. Odoo's own task views are honest about dates and silent about consequence: the task nobody can slip and the task with a fortnight in hand render identically, so a delay gets absorbed by whoever shouts loudest rather than by whoever actually has room. The usual answer is a JavaScript Gantt library billed per developer per year, which also puts the arithmetic in the browser, where no report and no automated action can ask which tasks are critical.

Platform
Odoo
Category
Planning boards
Works with
Odoo 18 · Odoo 19
Technical name
web_gantt_pro
Status
Direct from webbox
Pricing
Paid

What is inside it

  1. 01

    The critical path

    The longest chain of dependent work between the start and the finish, computed in Python from Odoo's own dependency links. Tasks off the chain carry a slack value in hours, and the chain is coloured red.

  2. 02

    No per-seat JS licence

    The chart is drawn by a bundled MIT-licensed component, its licence file alongside it, so nothing here carries a per-developer runtime fee that renews for as long as the module exists.

  3. 03

    The board

    Two scheduling fields added to project.task, a critical-path engine over the dependencies Odoo already models, and a Gantt view that draws both. No new models, and the tasks stay your tasks.

What it looks like in practice

  1. Documentation runs late and the finish date does not move

    Two branches of the plan run alongside the backend build and both finish before integration needs them. In a list they look as pressing as everything else.

    The engine walks the finish-to-start links and marks the chain that sets the end date. Everything off that chain gets a slack figure in hours, so the branch with room is named rather than guessed at.

    Tasks scheduled
    8
    On the critical path
    6
    Slack on the other two
    24h and 141h

    Figures from the module's own demo data, on a fresh install. Turn demo data on at install and open the demo project's Gantt view.

    The critical pathThe board

  2. A scheduled job needs to know a critical task is late

    Somebody wants an alert when work that sets the end date slips. The chart that shows criticality is rendered in a browser nobody has open at three in the morning.

    Criticality and slack are computed server-side and live on the task, so a filter, an automated action or an API call can read them with no front end involved.

    Behaviour of the shipped code.

    The critical pathNo per-seat JS licence

  3. A task with no dates stays off the chart

    Part of the backlog has never been scheduled. It is still in the project, and somebody expects to find it on the plan.

    A task is drawn once it has a Gantt start and a Gantt stop, and is absent until then, which is deliberate. Dragging its bar afterwards writes both dates back and moves whatever depends on it.

    Behaviour of the shipped code.

    The boardThe critical path

What it deliberately does not do

Finish-to-start only
Start-to-start, finish-to-finish and lead or lag times are not modelled. Odoo's own dependency field does not carry them either, and adding them would mean a second dependency model beside it.
No resource levelling
It tells you which tasks set the date. It will not reassign work to even out who is busy, and it will happily show one person on four simultaneous critical tasks.
No calendar or working-time awareness
Durations are elapsed hours. A task spanning a weekend is not stretched, so the span reported is calendar time rather than working time.
It does not replace Odoo's planning apps
For shift planning or forecasting, Enterprise ships its own apps. This answers a different question: which tasks set the finish date.

Questions

Can I install this on Odoo Online?
No. Odoo Online cannot install modules that contain Python, so this runs on Odoo.sh or a self-hosted instance. Check the versions listed above for the series and edition it is verified against.
Does it support start-to-start links or lead and lag times?
No, only finish-to-start, because that is the shape of dependency Odoo's own task field carries. Supporting the others would mean maintaining a second dependency model next to Odoo's, and the critical path would then be computed from links the rest of the system cannot see.
Is there a JavaScript library licence to buy on top?
No. The interactive chart is drawn by an MIT-licensed component bundled inside the module, with its licence file kept alongside it. There is no per-developer runtime fee renewing each year and no external service to call, so the module's own price covers all of it.
Who can see the Gantt, and does it add access groups?
It adds no access group and no menu of its own. A project user opens the Gantt for the projects they can already see, and the critical path is computed from those tasks, so the same record rules apply. A project manager dragging a bar writes the scheduling dates back to the task.

Have something to build?

Tell us the problem. We'll come back with a plan, a price, and who'd actually build it.

Start a project Browse services
  • Free scoping call
  • Reply within 1 business day
  • No lock-in