From a704f7bd8dc5a5035609eb73a5accb1e104d86f3 Mon Sep 17 00:00:00 2001
From: Antonin Bourguignon <abo@openerp.com>
Date: Fri, 1 Jun 2012 17:07:18 +0200
Subject: [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
---
 addons/project_issue/project_issue_data.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 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 8f0f097cb87..34fea22f9b9 100644
--- a/addons/project_issue/project_issue_data.xml
+++ b/addons/project_issue/project_issue_data.xml
@@ -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 -->
-- 
cgit v1.2.3