Project Work Breakdown Structure
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.
Table of contents
Usage
Create 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.
Known issues / Roadmap
Actions for the different account class are implemented but menus for those were not included. This is for inheritance purposes.
RTL-friendliness in Project codes and names
Do not show full names in children in Kanban View
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Eficent <http://www.eficent.com>
Luxim d.o.o. <http://www.luxim.si>
Matmoz d.o.o. <http://www.matmoz.si>
Deneroteam. <dhaval@deneroteam.com>
SerpentCS <http://www.serpentcs.com>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/project project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-project-wbs 15.0.1.2.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_project_wbs-15.0.1.2.0.4-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_project_wbs-15.0.1.2.0.4-py3-none-any.whl |
Release files / odoo_addon_project_wbs-15.0.1.2.0.4-py3-none-any.whl
| Download URL | odoo_addon_project_wbs-15.0.1.2.0.4-py3-none-any.whl |
|---|---|
| Size | 53.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d4152a7ecbb4e4f314d20ab8be1b9a69b87085ca4fdd64038ed4a472fd570cd1
|
|
BLAKE2b-256 checksum How to use checksums |
9c647b3ee3bf285dddd40fd54180f88ff36c4315609127f4279784ec35677b96
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-project-wbs 15.0.1.2.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
