diff --git a/addons/project/data/web_planner_data.xml b/addons/project/data/web_planner_data.xml
index 8e8bf631798..e40819c3198 100644
--- a/addons/project/data/web_planner_data.xml
+++ b/addons/project/data/web_planner_data.xml
@@ -1025,7 +1025,7 @@
                                             <strong>Exercise:</strong> Try to create a graph with the monthly evolution of the 'Average delay to close'  of Issues.
                                         </p>
                                         <li>
-                                            <a t-att-href="prepare_backend_url('project_issue.action_project_issue_report', 'graph', 'project_issue')">Issues analysis</a>
+                                            <a t-att-href="prepare_backend_url('project_issue.project_issue_action_analysis', 'graph', 'project_issue')">Issues analysis</a>
                                         </li>
                                     </div>
                                 </div>
diff --git a/addons/project_issue/report/project_issue_report_views.xml b/addons/project_issue/report/project_issue_report_views.xml
index 6178f6ba6fa..b897cf52191 100644
--- a/addons/project_issue/report/project_issue_report_views.xml
+++ b/addons/project_issue/report/project_issue_report_views.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <odoo>
-        <record id="view_project_issue_report_pivot" model="ir.ui.view">
+        <record id="project_issue_view_pivot" model="ir.ui.view">
             <field name="name">project.issue.pivot</field>
             <field name="model">project.issue</field>
             <field name="arch" type="xml">
@@ -11,7 +11,7 @@
             </field>
         </record>
 
-        <record id="view_project_issue_report_graph" model="ir.ui.view">
+        <record id="project_issue_view_graph" model="ir.ui.view">
             <field name="name">project.issue.graph</field>
             <field name="model">project.issue</field>
             <field name="arch" type="xml">
@@ -22,7 +22,7 @@
             </field>
         </record>
 
-        <record id="view_project_issue_report_filter" model="ir.ui.view">
+        <record id="project_issue_view_search" model="ir.ui.view">
             <field name="name">project.issue.search</field>
             <field name="model">project.issue</field>
             <field name="arch" type="xml">
@@ -45,32 +45,32 @@
             </field>
         </record>
 
-        <record id="action_project_issue_report" model="ir.actions.act_window">
+        <record id="project_issue_action_analysis" model="ir.actions.act_window">
             <field name="name">Issues Analysis</field>
             <field name="res_model">project.issue</field>
             <field name="view_type">form</field>
             <field name="view_mode">graph,pivot</field>
             <field name="context">{'search_default_year':1,'search_default_This Month':1,'search_default_project':1}</field>
-            <field name="search_view_id" ref="view_project_issue_report_filter"/>
+            <field name="search_view_id" ref="project_issue_view_search"/>
             <field name="view_ids" eval="[(5, 0, 0),
-                (0, 0, {'view_mode': 'pivot', 'view_id': ref('view_project_issue_report_pivot')}),
-                (0, 0, {'view_mode': 'graph', 'view_id': ref('view_project_issue_report_graph')})]"/>
+                (0, 0, {'view_mode': 'pivot', 'view_id': ref('project_issue_view_pivot')}),
+                (0, 0, {'view_mode': 'graph', 'view_id': ref('project_issue_view_graph')})]"/>
             <field name="help">This report on the project issues allows you to analyse the quality of your support or after-sales services. You can track the issues per age. You can analyse the time required to open or close an issue, the number of email to exchange and the time spent on average by issues.</field>
         </record>
 
         <!-- Custom reports (aka filters) -->
-        <record id="filter_issue_report_delay" model="ir.filters">
+        <record id="project_issue_filter_delay" model="ir.filters">
             <field name="name">Delay</field>
             <field name="model_id">project.issue</field>
             <field name="user_id" eval="False"/>
-            <field name="action_id" ref="action_project_issue_report"/>
+            <field name="action_id" ref="project_issue_action_analysis"/>
             <field name="context">{'group_by': ['project_id'], 'measures': ['delay_close', 'delay_open']}</field>
         </record>
-        <record id="filter_issue_report_responsible" model="ir.filters">
+        <record id="project_issue_filter_responsible" model="ir.filters">
             <field name="name">By Responsible</field>
             <field name="model_id">project.issue</field>
             <field name="user_id" eval="False"/>
-            <field name="action_id" ref="action_project_issue_report"/>
+            <field name="action_id" ref="project_issue_action_analysis"/>
             <field name="context">{'group_by': ['project_id', 'user_id']}</field>
         </record>
 
@@ -87,11 +87,11 @@
                 'default_project_id': active_id,
             }
             </field>
-            <field name="search_view_id" ref="view_project_issue_report_filter"/>
+            <field name="search_view_id" ref="project_issue_view_search"/>
             <field name="view_id"></field>  <!-- force empty -->
             <field name="help">This report on the project issues allows you to analyse the quality of your support or after-sales services. You can track the issues per age. You can analyse the time required to open or close an issue, the number of email to exchange and the time spent on average by issues.</field>
         </record>
 
-        <menuitem id="menu_project_issue_report_tree" action="action_project_issue_report"
+        <menuitem id="menu_project_issue_report_tree" action="project_issue_action_analysis"
             parent="project.menu_project_report" sequence="20"/>
 </odoo>