Most teams running Odoo Community hit the same wall: the planning views they need to see work over time simply are not there. Native list and kanban views tell you what exists and what state it is in, but they cannot show you a horizontal timeline of tasks, manufacturing orders, or leave against a calendar. The interactive Gantt view is an Enterprise-only web widget, so Community users are left exporting to spreadsheets or bolting on external tools, and even Enterprise sites often want Gantt on models that ship without it. The result is scheduling done in someone's head, overlapping commitments nobody catches until a deadline slips, and no shared picture of who is doing what, when.

Gantt View Base is a made-to-order module ECOSIRE builds for your database. It ports a reusable Gantt rendering layer onto the Odoo models you actually plan against — project.task, mro.production / mrp.production, hr.leave, or any custom model with a start and end date. Technically, we define a Gantt view type in the module's views (XML declaring date_start, date_stop, and the group-by fields), wire the OWL client widget and its assets bundle through the __manifest__.py, and back it with an ORM layer where computed @api.depends fields resolve durations, dependencies, and progress. Drag-to-reschedule writes straight back to the record through the standard ORM write(), so a bar you nudge on the timeline updates the underlying task dates, and any automated actions or constraints you already have still fire. Records are grouped by project, work center, employee, or team, and colored by state or a field you choose.

Because it is built on Odoo's own primitives, the module respects everything around it. Access is governed by ir.model.access.csv plus record rules, so people only see and drag the records they are entitled to; multi-company boundaries are honored; and the timeline reads and writes through the same XML-RPC / JSON-RPC surface your integrations already use. We can add dependency links (finish-to-start constraints between tasks), a critical-path highlight, capacity shading on resource rows, and a printable QWeb schedule report if your scope calls for it. Everything ships as clean, commented source in its own module so your team — or ours — can extend it later.

Delivery is build-to-order, not an instant download. We start with a short scoping call to confirm which models you want on a timeline, your Odoo edition and version (17.0, 18.0, or 19.0), and any dependency, capacity, or reporting rules. You get a fixed written quote and timeline before any build starts; typical delivery is one working week from confirmed scope. We build on a branch, hand it to you on staging for UAT, then install to production with a rollback plan. Pricing starts from $999 (indicative, single-company base scope); adding Gantt to additional or heavily customized models, dependency/critical-path logic, multi-company rollout, or data migration of existing schedules increases the quoted scope.