2 Sale Order views having same priority can confuse users

Bug #658650 reported by Ferdinand
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Fix Released
Low
Ravindra Mekhiya(OpenERP)

Bug Description

in V5 we have picked rate and invoiced rate (see openerp demo)

Related branches

Revision history for this message
Ferdinand (office-chricar) wrote :

and a field "Paid" would be useful to see the state of the "complete" flow

Revision history for this message
Ravindra Mekhiya(OpenERP) (rme-openerp) wrote :

Hello Ferdinand,

   I have checked the sale order tree view, but both the fields are present in the view. IMHO may be some customization might have been done at your end. Would you please update the code and recheck.

Thanks.

Changed in openobject-addons:
status: New → Invalid
Changed in openobject-addons:
milestone: none → 6.0
Revision history for this message
Ferdinand (office-chricar) wrote :

can't see picked/invoiced/paid in this view !?

Changed in openobject-addons:
status: Invalid → New
Revision history for this message
Ferdinand (office-chricar) wrote :

we have 2 views
SO takes
* sale.top.quotations.tree
instead of
* sale.order.tree
why
I created the db yesterday

Revision history for this message
Raphaël Valyi - http://www.akretion.com (rvalyi) wrote : Re: [Bug 658650] Re: [trunk] sale order - missing fields picked/invoiced in tree view

Ferdinand, I lost time just like you with this and even reported wrongly a
similar bug.

The issue IMHO is that those 2 views sale.top.quotations.tree and
sale.order.tree
have the same default "priority". So, depending on your updates, OpenERP can
take the wrong view.
IMHO OpenERP SA should set a lower priority to the main view: ale.order.tree

Can we have such a patch applied please?
I know at least 3 people now that have been loosing a few hours because of
this.

Raphaël Valyi.

On Wed, Oct 27, 2010 at 2:53 PM, Ferdinand @ ChriCar <
<email address hidden>> wrote:

> we have 2 views
> SO takes
> * sale.top.quotations.tree
> instead of
> * sale.order.tree
> why
> I created the db yesterday
>
> --
> [trunk] sale order - missing fields picked/invoiced in tree view
> https://bugs.launchpad.net/bugs/658650
> You received this bug notification because you are subscribed to
> OpenObject Addons.
>
> Status in OpenObject Addons Modules: New
>
> Bug description:
> in V5 we have picked rate and invoiced rate (see openerp demo)
>
>
>

Changed in openobject-addons:
assignee: nobody → RME(OpenERP) (rme-openerp)
Changed in openobject-addons:
status: New → Confirmed
summary: - [trunk] sale order - missing fields picked/invoiced in tree view
+ 2 Sale Order views having same priority can confuse users
Revision history for this message
Ravindra Mekhiya(OpenERP) (rme-openerp) wrote :

Hello Dr.Ferdinand & Raphaël Valyi,

It has been fixed by revision 4308 <email address hidden> in
https://code.launchpad.net/~openerp-commiter/openobject-addons/trunk-addons-fixes.

Thanks.

Changed in openobject-addons:
status: Confirmed → Fix Committed
Revision history for this message
Ferdinand (office-chricar) wrote :

there is a similar issue for o2m lists
IMHO we have no possibility to define which view should be taken in the xml code
workaround is possible manually defining the views for windows action

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Thanks Ferdinand and Raphael.
This has been fixed by revision 3876 <email address hidden>.
The O2M idea should come up as a wishlist.
Thanks RME.

Changed in openobject-addons:
status: Fix Committed → Fix Released
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.