addons/project_issue/project_issue_data.xml

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