From d4e9640e3428219c37115a320b4ec1e9cba2c169 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Thibault=20Delavall=C3=A9e?= <tde@openerp.com>
Date: Fri, 14 Nov 2014 14:53:54 +0100
Subject: [REF] mail: _track update.

_track is now a method that returns the subtype to trigger in a given
tracking context. A tracking will now lead to only one subtype
being trigerred, instead of having multiple possible subtypes.

Now, one tracking leads to one message with one subtype, or without subtype
if there is none matching. This simplifies the model for future evolution of
chatter and mail.

[IMP] project, project_issue: cleaned task and issue subtypes, now having
opened for created / assigned.
---
 addons/project_issue/project_issue_data.xml | 37 ++++++++++-------------------
 1 file changed, 12 insertions(+), 25 deletions(-)

(limited to 'addons/project_issue/project_issue_data.xml')

diff --git a/addons/project_issue/project_issue_data.xml b/addons/project_issue/project_issue_data.xml
index bcc80c006ee..2ed232be7a9 100644
--- a/addons/project_issue/project_issue_data.xml
+++ b/addons/project_issue/project_issue_data.xml
@@ -30,17 +30,11 @@ Access all issues from the top Project menu, and access the issues of a specific
 
         <!-- Issue-related subtypes for messaging / Chatter -->
         <record id="mt_issue_new" model="mail.message.subtype">
-            <field name="name">Issue Created</field>
+            <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 created</field>
-        </record>
-        <record id="mt_issue_assigned" model="mail.message.subtype">
-            <field name="name">Issue Assigned</field>
-            <field name="res_model">project.issue</field>
-            <field name="default" eval="False"/>
-            <field name="description">Issue assigned</field>
+            <field name="description">Issue opened</field>
         </record>
         <record id="mt_issue_blocked" model="mail.message.subtype">
             <field name="name">Issue Blocked</field>
@@ -49,10 +43,10 @@ Access all issues from the top Project menu, and access the issues of a specific
             <field name="description">Issue blocked</field>
         </record>
         <record id="mt_issue_ready" model="mail.message.subtype">
-            <field name="name">Issue Ready for Next Stage</field>
+            <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 Stage</field>
+            <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>
@@ -62,44 +56,37 @@ Access all issues from the top Project menu, and access the issues of a specific
         </record>
         <!-- Project-related subtypes for messaging / Chatter -->
         <record id="mt_project_issue_new" model="mail.message.subtype">
-            <field name="name">Issue Created</field>
+            <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_assigned" model="mail.message.subtype">
-            <field name="name">Issue Assigned</field>
+        <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_assigned')"/>
+            <field name="parent_id" eval="ref('mt_issue_blocked')"/>
             <field name="relation_field">project_id</field>
         </record>
-        <record id="mt_project_issue_blocked" model="mail.message.subtype">
-            <field name="name">Issue Blocked</field>
+        <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_blocked')"/>
+            <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>
-        <record id="mt_project_issue_ready" model="mail.message.subtype">
-            <field name="name">Issue Ready</field>
-            <field name="sequence">24</field>
-            <field name="res_model">project.project</field>
-            <field name="parent_id" eval="ref('mt_issue_ready')"/>
-            <field name="relation_field">project_id</field>
-            <field name="default" eval="False" />
-        </record>
         
     </data>
 </openerp>
-- 
cgit v1.2.3