Business Requirement Deliverable - Project
This module creates project tasks from the deliverables of a business requirement when it is approved, and links them to the requirement.
Each deliverable becomes a task. Its allocated time is the deliverable quantity when it is measured in time units.
Tasks can be created in an existing project, or in a new project created for the requirement.
Tasks get a Business Requirement field, which can be searched and grouped by, so tasks can also be linked by hand.
Business requirements get a Tasks smart button listing their tasks.
Table of contents
Usage
To create the tasks of a business requirement:
Go to Business Requirements and open a draft or confirmed requirement.
In On Approval, choose what to do with its deliverables:
Nothing: no task is created.
Create tasks in a project: choose the Project in which to create them.
Create a new project with tasks: a project named after the requirement is created when it is approved.
Approve the requirement, or move it straight to In progress or Done. A task is created for each deliverable.
If deliverables are added after the approval, click on Create Tasks to create their tasks. Deliverables which already have a task, even an archived one, don’t get a new one.
To see the tasks of a business requirement, click on its Tasks smart button. New tasks created from this list are linked to the requirement.
The On Approval and Project fields, and the Tasks smart button, are only shown to Project users. Tasks are created on approval anyway.
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
-
Oliver García
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/business-requirement 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-business-requirement-deliverable-project 18.0.1.0.0.1
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 | Reset |
|---|---|---|---|---|
| odoo_addon_business_requirement_deliverable_project-18.0.1.0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_business_requirement_deliverable_project-18.0.1.0.0.1-py3-none-any.whl
| Download URL | odoo_addon_business_requirement_deliverable_project-18.0.1.0.0.1-py3-none-any.whl |
|---|---|
| Size | 34.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4accba0738b4ac116919de06a1184989917c664eccf565ea1863c2135378f21f
|
|
BLAKE2b-256 checksum How to use checksums |
30f8a6a9bfc34d5940475ffa761bf7a0146d416eaa1d40ff73739f0dbdee3a07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-business-requirement-deliverable-project 18.0.1.0.0.1
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.
