Helpdesk Atomatic Stage Changes
Allows the configuration of the stages of a ticket. Customization of colors by stages and automatic stage changes when receiving or sending a message. The tickets will have customized colors according to the stage in the tree view.
In the ticket view, the possibility of sending an email from the ticket and a new tab where the email communications and notes associated with the ticket are recorded have been added. With the ability to create new notes, reply to a note, reply to an email without the emails in CC or with those.
Customization of colors depending on the type of communication:
-Black: Incoming message
-Green: Internal note
-Red: Outgoing message
Email sending goes through a new custom view for the helpdesk.ticket model.
Table of contents
Configuration
No configuration needed for this module.
Usage
En el modelo helpdesk.ticket.stage (menu: Helpdesk-Configuration-Stages) tienes la configuración.
En el model helpdesk.ticket (menu: Helpdesk-tickets) tienes la personalización de la vista.
Known issues / Roadmap
There are no issues for the moment.
Bug Tracker
Bugs are tracked on GitLab 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
-
Álvaro García <alvaro.garcia@somit.coop>
José Robles <jose.robles@somit.coop>
-
Gerard Funosas <gerard.funosas@somconnexio.coop>
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.
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-crm-lead-dms-category 12.0.0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| odoo12-addon-crm_lead_dms_category-12.0.0.1.0.tar.gz | 18.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| odoo12_addon_crm_lead_dms_category-12.0.0.1.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 39.3 kB
Release files / odoo12-addon-crm_lead_dms_category-12.0.0.1.0.tar.gz
| Download URL | odoo12-addon-crm_lead_dms_category-12.0.0.1.0.tar.gz |
|---|---|
| Size | 18.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ab7ed96fcd808abfcc670c5523cbdf98bf73c66ff322de01c37f5fdc14c83864
|
|
BLAKE2b-256 checksum How to use checksums |
ec1c350b50fd43603f51dae4c25f69b9ceb4a7fe009112dc1e8e65cef09ecf61
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.8.2
|
Release files / odoo12_addon_crm_lead_dms_category-12.0.0.1.0-py2.py3-none-any.whl
| Download URL | odoo12_addon_crm_lead_dms_category-12.0.0.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 20.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
03c9708a8b16066bded8492b8ceb1226a2d2901e987639a23522504b2b7cc26d
|
|
BLAKE2b-256 checksum How to use checksums |
5b7a251e01d4af55f7bd639e3842106fd2b286904f5c3b834512cb90b9881156
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.8.2
|
Security for odoo12-addon-crm-lead-dms-category 12.0.0.1.0
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.
