[6.0.2] Inconsistent process in Warehouse with lots and split lots
Bug #807578 reported by
Juan Márquez
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Odoo Web Client |
Won't Fix
|
Low
|
OpenERP R&D Web Team | ||
Bug Description
In:
Warehouse -> Warehouse Management -> Incoming Shipments (Stock Moves -> New)
When I use then web client the Scarp, Pack & Split buttons are active, in GTK Don't
Also If I try to split a lot I have several errors:
* The wizard don't show the product info (until i save the stock move)
* The Quantity (in Stock Move Wizard) dosen't updated with the sum of "splited" lots
* If I split lots before save the stock move, this lots are missing.
Note: I set "Track Incoming Lots" and "Track Outgoing Lots" to True in product definition
Revision history for this message
| Vishal Parmar(Open ERP) (vpa-openerp) wrote | #1 |
| affects: | openobject-addons → openobject-client-web |
| Changed in openobject-client-web: | |
| assignee: | nobody → OpenERP R&D Web Team (openerp-dev-web) |
| importance: | Undecided → Low |
| status: | New → Confirmed |
Revision history for this message
| OpenERP Majordomo (openerp-majordomo) wrote OpenERP Majordomo Message | #2 |
| Changed in openobject-client-web: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
**automated message**
Thanks a lot for reporting this bug and contributing to OpenERP. Unfortunately the OpenERP Web Client project is not going to be developed further after the 6.0 series. As of 6.1 a newer and better web frontend known as the OpenERP Web project[1] will be available.
Our R&D developers normally work in Launchpad to fix bugs for the next release, but there will be no next release for the current OpenERP Web Client. As our resources are limited, all further R&D efforts from the Web team are dedicated to finish the new 6.1 OpenERP Web project[1].
This bug will be closed as "Won't Fix" to show that R&D won't be able to work on it.
Bugs affecting customers in production of course continue to be handled via the OpenERP Enterprise (OPW) maintenance service, and this is the recommended way to have them corrected directly in the 6.0 LTS stable branch.
You can find more details about all of this in the FAQ of our Bug Management Policy documentation[2].
If you are interested, you should soon be able to beta-test the new OpenERP Web 6.1 (this will be announced on OpenERP Community channels).
Thank you for your contributions and for your understanding!
[1] https:/
[2] http://