Sequence in product.packaging is not used for sort [5.0]

[Niels Huylebroeck]

The model does not define an _order = "sequence"

So when in the code in product_id_change (in sale.order.line) is executed the the result of the call to:

        if not packaging and product_obj.packaging:
            packaging = product_obj.packaging[0].id
            result['product_packaging'] = packaging

... will yield the packaging to be the first inserted record instead of taking lowest sequenced packaging.

[Nhomar - Vauxoo (nhomar)]

Niels?.

Don't you think "fix-commited" will be when your branch has been merged? I
think the state should be "in progress"

THX

2010/6/21 Niels Huylebroeck <email address hidden>

> ** Changed in: openobject-addons
> Status: New => Fix Committed
>
> --
> Sequence in product.packaging is not used for sort [5.0]
> https://bugs.launchpad.net/bugs/596940
> You received this bug notification because you are a member of OpenERP
> Drivers, which is subscribed to OpenObject Addons.
>
> Status in OpenObject Addons Modules: Fix Committed
>
> Bug description:
> The model does not define an _order = "sequence"
>
> So when in the code in product_id_change (in sale.order.line) is executed
> the the result of the call to:
>
> if not packaging and product_obj.packaging:
> packaging = product_obj.packaging[0].id
> result['product_packaging'] = packaging
>
> ... will yield the packaging to be the first inserted record instead of
> taking lowest sequenced packaging.
>
>
>

--
Saludos Cordiales

Nhomar G. Hernandez M.
[phone]
[phone]
[phone] ext 124
[phone]
Skype: nhomar00
Web-Blog: http://geronimo.com.ve
Servicios IT: http://openerp.netquatro.com
Linux-Counter: 467724
Correos:
<email address hidden>
<email address hidden>

[Niels Huylebroeck (red15)]

Don't know honestly, you still have fix-released though, so maybe when
merge is accepted then it should be fix-released ?

Because I dont think OpenERP goes around at the time of release and only
setting bugs to fix-released when they do a release.

They set it already to released as soon as it's in the stable.

If not I hope someone from OpenERP will tell me and I'll adjust to their
preferences.

Regards,
Niels

Nhomar Hernández - http://openerp.netquatro.com wrote:
> Niels?.
>
> Don't you think "fix-commited" will be when your branch has been merged? I
> think the state should be "in progress"
>
> THX
>
> 2010/6/21 Niels Huylebroeck <email address hidden>
>
>
>> ** Changed in: openobject-addons
>> Status: New => Fix Committed
>>
>> --
>> Sequence in product.packaging is not used for sort [5.0]
>> https://bugs.launchpad.net/bugs/596940
>> You received this bug notification because you are a member of OpenERP
>> Drivers, which is subscribed to OpenObject Addons.
>>
>> Status in OpenObject Addons Modules: Fix Committed
>>
>> Bug description:
>> The model does not define an _order = "sequence"
>>
>> So when in the code in product_id_change (in sale.order.line) is executed
>> the the result of the call to:
>>
>> if not packaging and product_obj.packaging:
>> packaging = product_obj.packaging[0].id
>> result['product_packaging'] = packaging
>>
>> ... will yield the packaging to be the first inserted record instead of
>> taking lowest sequenced packaging.
>>
>>
>>
>>
>
>
>

[Olivier Dony (Odoo) (odo-openerp)]

Fix merged in revision 2763 <email address hidden> in addons-5.0.
It was already fixed in trunk.

Note: to answer your question, we don't use 'Fix Committed' a lot, we set to 'Fix Released' when the fix has landed on official branches, which means it's getting released with the next patch release. In most case you should probably set the status to 'In progress' until that happens unless you are very sure that the fix you proposed for merging is going to be accepted (which was indeed the case here).