Antonin Bourguignon
a704f7bd8d
- give read access rights to group_portal_member on projet.task.type and project.task.work models - hide action buttons and priority fields in form and list views - a question remains: how to handle states and stages ? state seems more revelant and simple to understand for portal users (and therefore should be shown through the statusbar widget) while stage is more interesing for internal organization bzr revid: abo@openerp.com-20120601150718-dk49583g1tko118y
36 lines
1.2 KiB
XML
36 lines
1.2 KiB
XML
<?xml version="1.0"?>
|
|
<openerp>
|
|
<data noupdate="1">
|
|
|
|
<!-- Case Categories -->
|
|
<!-- For Bugs -->
|
|
|
|
<record model="crm.case.categ" id="bug_categ">
|
|
<field name="name">Maintenance</field>
|
|
<field name="section_id" ref="crm.section_sales_department"/>
|
|
<field name="object_id" search="[('model','=','project.issue')]" model="ir.model"/>
|
|
</record>
|
|
|
|
<record model="crm.case.categ" id="feature_request_categ">
|
|
<field name="name">Feature Requests</field>
|
|
<field name="section_id" ref="crm.section_sales_department"/>
|
|
<field name="object_id" search="[('model','=','project.issue')]" model="ir.model"/>
|
|
</record>
|
|
|
|
<!-- Case type_id -->
|
|
<!-- For Bugs -->
|
|
<record model="project.issue.version" id="type1">
|
|
<field name="name">v1.0</field>
|
|
</record>
|
|
|
|
<record model="project.issue.version" id="type2">
|
|
<field name="name">v2.0</field>
|
|
</record>
|
|
|
|
<record model="project.issue.version" id="type3">
|
|
<field name="name">v3.0</field>
|
|
</record>
|
|
|
|
</data>
|
|
</openerp>
|