Adding WBS information to Odoo Projects
- The hierarchy of a project is considered the WBS (Work Breakdown Structure)
- The analytic accounts in the project hierarchies are considered WBS components
- The analytic account code is shown in the project
- The complete WBS path code is shown in the analytic account and in the project
- The complete WBS path name is shown in the analytic account and in the project
- The WBS paths are concatenated with each other
- Project Manager is propagated to the hierarchy, the Manager is Manager for the WBS element only
Searching and Browsing WBS
- It is possible to search projects by complete WBS path code & name
- It is possible to search tasks by project complete WBS path code & name
- The WBS components can be classified as project, phase, deliverable, work package.
- The classification is shown in the project and analytic account views
- A project stage attribute is incorporated in the analytic account and displayed in the project and analytic account views.
auto_awesome What this module does
AI-generated from the code · Odoo 15.0Organise projects as a Work Breakdown Structure (WBS) with parent/child levels, full WBS codes and paths, and classify each element as project, phase, deliverable or work package.
This module turns the project hierarchy into a Work Breakdown Structure. Each project is linked to an analytic account, and the parent/child links between those accounts define the WBS levels. On every project and analytic account you can set a Class: Project, Phase, Deliverable or Work Package.
Odoo automatically builds a full WBS code and full WBS path by joining the codes and names of all parents, shown on the project and analytic account forms, lists and searches. A unique constraint prevents two elements from sharing the same full WBS code.
A new WBS menu appears under the Project menu, with dedicated views for WBS elements, WBS overview, Projects, Phases, Deliverables and Work Packages. In the project form a Work Breakdown Structure tab lists child elements and offers a Create child WBS element button. Kanban and tree views show up/down navigation buttons to move between a parent and its children.
Business rules: duplicating an analytic account that has projects is blocked (duplicate the project instead); changing the project manager on a project propagates that manager to all child analytic accounts; activating or deactivating an analytic account follows its projects; and the project's parent, code, class and root analytic account stay in sync with the analytic account.
Depends on
Required by other modules
Menus it adds
Models and fields (2)
- project.project · extends an existing modelcode, child_ids, parent_id, wbs_indent, account_class, complete_wbs_code (WBS Code), complete_wbs_name, analytic_account_id, project_analytic_id, project_child_complete_ids (Project Hierarchy), has_project_child_complete_ids
- account.analytic.account · extends an existing modelcode, user_id, parent_id (Parent Analytic Account), manager_id, partner_id, wbs_indent (Level), project_ids (Projects), account_class, complete_wbs_code (Full WBS Code), complete_wbs_name (Full WBS path), project_analytic_id (Root Analytic Account)
Text generated by AI (DeepSeek) from reading the Odoo 15.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/project.
terminal Installation and usage
OCA documentation · Odoo 15.0Usage
Source · Odoo 15.0Create a new child:
- Go to Project > WBS
- Click on one existing project or create a new one
- Click on the form view to open the project.
- Go to Work Breakdown Structure to create a new child
Navigation:
- Level column indicates the child hierarchy: '>' means it is a child. '>>' means it is a grandchild an so on.
- Click on the up arrow to see the parent project.
- Click on the down arrow to see children projects.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.