This commit slightly reworks the "event_track_template_new" template to format it a little better and get rid of unnecessary blank sections. The "subject" param was removed from the "message_post_with_view" call as we don't want the chatter to contain the name of the track twice. Indeed, since #61570, the "subject" is displayed in the chatter if it differs from the thread name (which is the case here). This causes a small regression for emails that will state "Re: EventName" in their subject instead of the track name, but it's deemed acceptable to have a nicer chatter message. We also remove the description of the "mt_event_track" mail.message.subtype as it's only used with a custom template and is redundant with that template's content. Task-2496444 closes odoo/odoo#68864 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
26 lines
1.0 KiB
XML
26 lines
1.0 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo><data noupdate="1">
|
|
<!-- Event-related subtypes for new track / Chatter -->
|
|
<record id="mt_event_track" model="mail.message.subtype">
|
|
<field name="name">New Track</field>
|
|
<field name="res_model">event.event</field>
|
|
<field name="default" eval="False"/>
|
|
</record>
|
|
|
|
<!-- Track subtypes -->
|
|
<record id="mt_track_blocked" model="mail.message.subtype">
|
|
<field name="name">Track Blocked</field>
|
|
<field name="res_model">event.track</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="internal" eval="True"/>
|
|
<field name="description">Track blocked</field>
|
|
</record>
|
|
<record id="mt_track_ready" model="mail.message.subtype">
|
|
<field name="name">Track Ready</field>
|
|
<field name="res_model">event.track</field>
|
|
<field name="default" eval="True"/>
|
|
<field name="internal" eval="True"/>
|
|
<field name="description">Track Ready for Next Stage</field>
|
|
</record>
|
|
</data></odoo>
|