Thibault Delavallée
2c36354ca9
model has been renamed to mail.channel to prepare the slack modeling. In future commits the mail.group model will be merged with the channel model from im_chat. The first move is to rename mail.group into mail.channel to have a model that will unite both features.
79 lines
4.0 KiB
XML
79 lines
4.0 KiB
XML
<?xml version="1.0"?>
|
|
<openerp>
|
|
<data noupdate="1">
|
|
|
|
<!-- notify all employees of module installation -->
|
|
<record model="mail.message" id="module_install_notification">
|
|
<field name="model">mail.channel</field>
|
|
<field name="res_id" ref="mail.channel_all_employees"/>
|
|
<field name="message_type">notification</field>
|
|
<field name="subtype_id" ref="mail.mt_comment"/>
|
|
<field name="subject">Issue Tracker application installed!</field>
|
|
<field name="body"><![CDATA[<p>Manage the issues you might face in a project, such as bugs in a system, client complaints or material breakdowns.</p><p>
|
|
You can record issues, assign them to a responsible person, and keep track of their status as they evolve over time.</p><p>
|
|
Access all issues from the top Project menu, and access the issues of a specific project via the projects gallery view.</p>]]></field>
|
|
</record>
|
|
|
|
<!-- Issue-related subtypes for messaging / Chatter -->
|
|
<record id="mt_issue_new" model="mail.message.subtype">
|
|
<field name="name">Issue Opened</field>
|
|
<field name="res_model">project.issue</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="hidden" eval="True"/>
|
|
<field name="description">Issue opened</field>
|
|
</record>
|
|
<record id="mt_issue_blocked" model="mail.message.subtype">
|
|
<field name="name">Issue Blocked</field>
|
|
<field name="res_model">project.issue</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="description">Issue blocked</field>
|
|
</record>
|
|
<record id="mt_issue_ready" model="mail.message.subtype">
|
|
<field name="name">Issue Ready</field>
|
|
<field name="res_model">project.issue</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="description">Issue ready for next sStage</field>
|
|
</record>
|
|
<record id="mt_issue_stage" model="mail.message.subtype">
|
|
<field name="name">Stage Changed</field>
|
|
<field name="res_model">project.issue</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="description">Stage changed</field>
|
|
</record>
|
|
<!-- Project-related subtypes for messaging / Chatter -->
|
|
<record id="mt_project_issue_new" model="mail.message.subtype">
|
|
<field name="name">Issue Opened</field>
|
|
<field name="sequence">20</field>
|
|
<field name="res_model">project.project</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="parent_id" eval="ref('mt_issue_new')"/>
|
|
<field name="relation_field">project_id</field>
|
|
</record>
|
|
<record id="mt_project_issue_blocked" model="mail.message.subtype">
|
|
<field name="name">Issue Blocked</field>
|
|
<field name="sequence">21</field>
|
|
<field name="res_model">project.project</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="parent_id" eval="ref('mt_issue_blocked')"/>
|
|
<field name="relation_field">project_id</field>
|
|
</record>
|
|
<record id="mt_project_issue_ready" model="mail.message.subtype">
|
|
<field name="name">Issue Ready</field>
|
|
<field name="sequence">22</field>
|
|
<field name="res_model">project.project</field>
|
|
<field name="parent_id" eval="ref('mt_issue_ready')"/>
|
|
<field name="relation_field">project_id</field>
|
|
</record>
|
|
<record id="mt_project_issue_stage" model="mail.message.subtype">
|
|
<field name="name">Issue Stage Changed</field>
|
|
<field name="sequence">23</field>
|
|
<field name="res_model">project.project</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="description">Stage changed</field>
|
|
<field name="parent_id" eval="ref('mt_issue_stage')"/>
|
|
<field name="relation_field">project_id</field>
|
|
</record>
|
|
|
|
</data>
|
|
</openerp>
|