addons/project_issue/project_issue_data.xml

   1 <?xml version="1.0"?>
   2 <openerp>
   3     <data noupdate="1">
   4
   5         <!-- Case type_id -->
   6         <!--    For Bugs    -->
   7         <record model="project.issue.version" id="type1">
   8             <field name="name">v1.0</field>
   9         </record>
  10
  11         <record model="project.issue.version" id="type2">
  12             <field name="name">v2.0</field>
  13         </record>
  14
  15         <record model="project.issue.version" id="type3">
  16             <field name="name">v3.0</field>
  17         </record>
  18
  19         <!-- notify all employees of module installation -->
  20         <record model="mail.message" id="module_install_notification">
  21             <field name="model">mail.group</field>
  22             <field name="res_id" ref="mail.group_all_employees"/>
  23             <field name="type">notification</field>
  24             <field name="subtype_id" ref="mail.mt_comment"/>
  25             <field name="subject">Issue Tracker application installed!</field>
  26             <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>
  27 You can record issues, assign them to a responsible person, and keep track of their status as they evolve over time.</p><p>
  28 Access all issues from the top Project menu, and access the issues of a specific project via the projects gallery view.</p>]]></field>
  29         </record>
  30
  31         <!-- Issue-related subtypes for messaging / Chatter -->
  32         <record id="mt_issue_new" model="mail.message.subtype">
  33             <field name="name">Issue Created</field>
  34             <field name="res_model">project.issue</field>
  35             <field name="default" eval="False"/>
  36             <field name="hidden" eval="True"/>
  37             <field name="description">Issue created</field>
  38         </record>
  39         <record id="mt_issue_assigned" model="mail.message.subtype">
  40             <field name="name">Issue Assigned</field>
  41             <field name="res_model">project.issue</field>
  42             <field name="default" eval="False"/>
  43             <field name="description">Issue assigned</field>
  44         </record>
  45         <record id="mt_issue_blocked" model="mail.message.subtype">
  46             <field name="name">Issue Blocked</field>
  47             <field name="res_model">project.issue</field>
  48             <field name="default" eval="False"/>
  49             <field name="description">Issue blocked</field>
  50         </record>
  51         <record id="mt_issue_ready" model="mail.message.subtype">
  52             <field name="name">Issue Ready for Next Stage</field>
  53             <field name="res_model">project.issue</field>
  54             <field name="default" eval="False"/>
  55             <field name="description">Issue Ready for Next Stage</field>
  56         </record>
  57         <record id="mt_issue_stage" model="mail.message.subtype">
  58             <field name="name">Stage Changed</field>
  59             <field name="res_model">project.issue</field>
  60             <field name="default" eval="False"/>
  61             <field name="description">Stage changed</field>
  62         </record>
  63         <!-- Project-related subtypes for messaging / Chatter -->
  64         <record id="mt_project_issue_new" model="mail.message.subtype">
  65             <field name="name">Issue Created</field>
  66             <field name="sequence">20</field>
  67             <field name="res_model">project.project</field>
  68             <field name="default" eval="False"/>
  69             <field name="parent_id" eval="ref('mt_issue_new')"/>
  70             <field name="relation_field">project_id</field>
  71         </record>
  72         <record id="mt_project_issue_assigned" model="mail.message.subtype">
  73             <field name="name">Issue Assigned</field>
  74             <field name="sequence">21</field>
  75             <field name="res_model">project.project</field>
  76             <field name="default" eval="False"/>
  77             <field name="parent_id" eval="ref('mt_issue_assigned')"/>
  78             <field name="relation_field">project_id</field>
  79         </record>
  80         <record id="mt_project_issue_blocked" model="mail.message.subtype">
  81             <field name="name">Issue Blocked</field>
  82             <field name="sequence">22</field>
  83             <field name="res_model">project.project</field>
  84             <field name="parent_id" eval="ref('mt_issue_blocked')"/>
  85             <field name="relation_field">project_id</field>
  86         </record>
  87         <record id="mt_project_issue_stage" model="mail.message.subtype">
  88             <field name="name">Issue Stage Changed</field>
  89             <field name="sequence">23</field>
  90             <field name="res_model">project.project</field>
  91             <field name="description">Stage changed</field>
  92             <field name="parent_id" eval="ref('mt_issue_stage')"/>
  93             <field name="relation_field">project_id</field>
  94         </record>
  95         <record id="mt_project_issue_ready" model="mail.message.subtype">
  96             <field name="name">Issue Ready</field>
  97             <field name="sequence">24</field>
  98             <field name="res_model">project.project</field>
  99             <field name="parent_id" eval="ref('mt_issue_ready')"/>
 100             <field name="relation_field">project_id</field>
 101             <field name="default" eval="False" />
 102         </record>
 103
 104     </data>
 105 </openerp>