This release is a pre-release and may not be stable for production use.
The Responsible (user_id) field is made read only, and can instead be changed through a wizard, accessible only to Project Users.
Regular users (Employee group) will be able to see who is handling the request, but won’t be able to change it.
Project Users can click on the “=> Reassign” link, in front of the current responsible, to open a dialog where they can select the new responsible and/or new Project/Service Team it should be assigned to.
Mass reassignments can also be made, through the context menu action on the Issues list view.
Credits
Contributors
Daniel Reis
Maintainer
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.
To contribute to this module, please visit http://odoo-community.org.
Metadata
Release files for odoo8-addon-project-issue-reassign 8.0.1.1.0.99.dev14
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 |
|---|---|---|---|---|
| odoo8_addon_project_issue_reassign-8.0.1.1.0.99.dev14-py2-none-any.whl | Python 2 | none | any | Details for odoo8_addon_project_issue_reassign-8.0.1.1.0.99.dev14-py2-none-any.whl |
Release files / odoo8_addon_project_issue_reassign-8.0.1.1.0.99.dev14-py2-none-any.whl
| Download URL | odoo8_addon_project_issue_reassign-8.0.1.1.0.99.dev14-py2-none-any.whl |
|---|---|
| Size | 91.3 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
e1a38898bc4e6a8779d0470be5b241396aaa2683bae6fb95e3293c30f7b49968
|
|
BLAKE2b-256 checksum How to use checksums |
76aac9ec35ad6f02e4cb5b82134eeb099042d06ec31128eb21813b7dd9f6f018
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for odoo8-addon-project-issue-reassign 8.0.1.1.0.99.dev14
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.