This is a technical module for adding some HR information to projects and provide technical fields with HR information:
Employee categories at project and task level.
Employee linked to the user assigned to a task.
Employee categories at user level.
These fields can be used later for extra features like task scheduling or security restrictions.
It also provides some facilities on project management:
Limit selection of assigned users according selected employee category at task level.
Limit selection of employee categories at task level depending on the selected categories at project level. All are shown if no categories at project level.
Table of contents
Configuration
For setting employee categories at project level:
Go to Project > Projects.
Click on the 3 vertical dots of one of the project kanban cards for unfolding options and select “Edit”.
Put the wanted employee categories on the field “Employee Categories”.
For setting employee categories:
Go to Project > All Tasks.
Select or create a new task.
Put the wanted employee categories on the field “Employee categories”.
If there’s already some employee categories selected at project level, those will be the only selectable ones in the task.
Usage
Go to Project > Search > Tasks.
If there’s an employee category selected in the task, you will only be able to select those users whose employee belongs to that category.
Known issues / Roadmap
Limit project and task visibility according employee categories through overriding security methods (as through record rules is not possible without modifying existing ones).
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 smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
-
Pedro M. Baeza
Victor M.M. Torres
Alexey Pelykh <alexey.pelykh@brainbeanapps.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 odoo12-addon-project-hr 12.0.1.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 | Actions Reset |
|---|---|---|---|---|
| odoo12_addon_project_hr-12.0.1.0.1-py3-none-any.whl | Python 3 | none | any | Details for odoo12_addon_project_hr-12.0.1.0.1-py3-none-any.whl |
Release files / odoo12_addon_project_hr-12.0.1.0.1-py3-none-any.whl
| Download URL | odoo12_addon_project_hr-12.0.1.0.1-py3-none-any.whl |
|---|---|
| Size | 33.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fb332a207bd0865596e40b3778cbe5433a341756deb1a66f09473e9749a2d653
|
|
BLAKE2b-256 checksum How to use checksums |
a512ef1b4ce15e42eb93e8510d6f4c6e7dd2437b685af28d8e18c86ef394f7c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3
|
Security for odoo12-addon-project-hr 12.0.1.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.
