Comment 8 for bug 532148
Revision history for this message
| Olivier Dony (Odoo) (odo-openerp) wrote | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
Hello,
Sorry, this bug had fallen outside of our bug management radar (due to being assigned to an individual), thanks to Joel for helping dig it out.
Let's have an update on the status:
- in 6.0 and trunk this cannot be reproduced at all - I just tried again in trunk and 6.0.3 with the steps described by Don, and it works fine. I also tried with a minimum stock rule (order point) and it works fine too - it can trigger multiple procurements.
- the reason why it works in 6.0 and trunk is because in 6.0 we changed the procurements to automatically turn on the 'auto_validate' flag of their stock move when the move is created[1]. This happens when it is confirmed, except when the stock move was already created. This last case is important because it allows the make-to-order (MTO) flows: when the procurement is created by a sale order containing an MTO product, you don't want the procurement to complete and the customer delivery to happen automatically when the products are received from the supplier!
Based on the above:
@MarianTheisen: I do not understand your comments for 6.0. Could you be more specific, and perhaps provide some steps to reproduce? The steps in the bug description do not produce the bug in 6.0.3 for me.
@Joel, you confirm that 5.0 still has the problem, but could you be more specific as to why you say that this is "preventing the company to order product the next time a customer order it". Are you talking about minimum stock rules? Can you perhaps provide simple steps to reproduce? Based on that we could accept a high priority to the bug in 5.0 - and assign it to the relevant team (you know the policy)
@Don, I'm terribly sorry I failed to follow-up on the merge proposal - this is probably due to the change of our internal bug management process[2], where verified bugs are now assigned to predefined teams . Luckily we fixed the bug in the mean time in 6.0/trunk, and the test you provided is now converted as a YAML test in the purchase module (please double-check [3], but I think it is the case). Thanks a lot for your excellent contribution, as always!
[1] addons revision <email address hidden> : http://
[2] http://
[3] http://