diff options
| author | Dharmraj Jhala <dja@odoo.com> | 2020-08-06 09:47:56 +0000 |
|---|---|---|
| committer | Thibault Delavallée <tde@odoo.com> | 2020-08-27 14:30:00 +0000 |
| commit | 2ebbeb4b5443c6405dd9a3b202a1eee9c5c67ebb (patch) | |
| tree | 97213f93861f8b44e744e24543229aec5ca89613 /addons/crm/data | |
| parent | 910559c092dc7dfa00b91339a5423e16cd4668e1 (diff) | |
[FIX] mail, crm: do not display body in creation message when having a subtype
Right now on few business objects (like leads, invoices, tasks, helpdesk
tickets etc) creation message contains
* subtype description;
* generic creation message;
This looks like multiple creation message on chatter after creation of the
record as you generally have "Task Created - Task created" (subtype description
then generic message).
This happens when we provide custom subtype on creation by by overriding
`_creation_subtype` method.
This commit fixes the issue by only using provided creation subtype and
removing default body. If creation subtype is not provided default creation
message is posted as before.
In this commit we also fix subtype for Lead/Opportunity creation and make
it generic ('Lead/Opportunity created') to avoid inconsistent behavior.
Finally some cleaning is made in method naming. Semi followup of 92e9e84b63a266b39d556c1db1d336373dc8b303
LINKS
Task ID-2288458
PR odoo/odoo#56631
PR odoo/enterprise#12707
Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
Diffstat (limited to 'addons/crm/data')
| -rw-r--r-- | addons/crm/data/mail_data.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/addons/crm/data/mail_data.xml b/addons/crm/data/mail_data.xml index 28253e529b5..d6e6015e2a5 100644 --- a/addons/crm/data/mail_data.xml +++ b/addons/crm/data/mail_data.xml @@ -15,7 +15,7 @@ <field name="hidden" eval="True"/> <field name="res_model">crm.lead</field> <field name="default" eval="False"/> - <field name="description">Opportunity created</field> + <field name="description">Lead/Opportunity created</field> </record> <record id="mt_lead_stage" model="mail.message.subtype"> <field name="name">Stage Changed</field> |