diff --git a/addons/portal_claim/portal_claim_view.xml b/addons/portal_claim/portal_claim_view.xml
index ce1efc10f70..86be0764d26 100644
--- a/addons/portal_claim/portal_claim_view.xml
+++ b/addons/portal_claim/portal_claim_view.xml
@@ -2,8 +2,19 @@
 <openerp>
     <data>
 
+        <record id="crm_case_categ_claim0" model="ir.actions.act_window">
+            <field name="name">Claims</field>
+            <field name="res_model">crm.claim</field>
+            <field name="view_type">form</field>
+            <field name="view_mode">tree,calendar,form</field>
+            <field name="view_id" ref="crm_claim.crm_case_claims_tree_view"/>
+            <field name="context">{"search_default_user_id":'', "stage_type":'claim'}</field>
+            <field name="search_view_id" ref="crm_claim.view_crm_case_claims_filter"/>
+            <field name="help">Record and track your customers' claims. Claims may be linked to a sales order or a lot. You can send emails with attachments and keep the full history for a claim (emails sent, intervention type and so on). Claims may automatically be linked to an email address using the mail gateway module.</field>
+        </record>
+
         <menuitem name="Claims" id="portal_after_sales_claims" parent="portal.portal_after_sales" 
-            action="crm_claim.crm_case_categ_claim0" sequence="10"/>
+            action="crm_case_categ_claim0" sequence="10"/>
 
     </data>
 </openerp>
diff --git a/addons/portal_project_issue/portal_project_issue_view.xml b/addons/portal_project_issue/portal_project_issue_view.xml
index 73a28f9f0bb..fdbf1037c20 100644
--- a/addons/portal_project_issue/portal_project_issue_view.xml
+++ b/addons/portal_project_issue/portal_project_issue_view.xml
@@ -2,8 +2,20 @@
 <openerp>
     <data>
 
+        <record id="project_issue_categ_act0" model="ir.actions.act_window">
+            <field name="name">Issues</field>
+            <field name="res_model">project.issue</field>
+            <field name="view_type">form</field>
+            <field name="view_mode">kanban,tree,calendar</field>
+            <field name="view_id" eval="False"/>
+            <field name="domain" eval=""/>
+            <field name="context">{"search_default_user_id":'', "search_default_draft":'', "search_default_todo":''}</field>
+            <field name="search_view_id" ref="project_issue.view_project_issue_filter"/>
+            <field name="help">Issues such as system bugs, customer complaints, and material breakdowns are collected here. You can define the stages assigned when solving the project issue (analysis, development, done). With the mailgateway module, issues can be integrated through an email address (example: support@mycompany.com)</field>
+        </record>
+
         <menuitem name="Issues" id="portal_after_sales_issues" parent="portal.portal_projects"
-            action="project_issue.project_issue_categ_act0" sequence="10"/>
+            action="project_issue_categ_act0" sequence="10"/>
 
     </data>
 </openerp>