[IMP] adapt task and issue views for portal users
- 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
This commit is contained in:
@@ -8,13 +8,13 @@
|
||||
<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"/>
|
||||
<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"/>
|
||||
<field name="object_id" search="[('model','=','project.issue')]" model="ir.model"/>
|
||||
</record>
|
||||
|
||||
<!-- Case type_id -->
|
||||
|
||||
Reference in New Issue
Block a user