developer unfriendly behaviour of menu - view definition

Registered by Ferdinand

Example sales
after creating a customised special view (new name) - all the original menu entries use the new one - which is not the intended behaviour.
to regain the functionality of the original module it is necessary to define the following code for every menu entry ( I know this will be easier in V6 as not so many menu entries will exist)

I just want to ask if it is not possible to retain the default behaviour .

    <!-- Quotation -->
    <record model="ir.actions.act_window.view" id="chricar_stock_view_order_tree5">
      <field name="sequence" eval="1"/>
      <field name="view_mode">tree</field>
      <field name="view_id" ref="sale.view_order_tree"/>
      <field name="act_window_id" ref="sale.action_order_tree5"/>
    </record>
    <record model="ir.actions.act_window.view" id="chricar_stock_view_order_form5">
      <field name="sequence" eval="2"/>
      <field name="view_mode">form</field>
      <field name="view_id" ref="sale.view_order_form"/>
      <field name="act_window_id" ref="sale.action_order_tree5"/>
    </record>

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.