← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 784434] [NEW] [6.0.2 bzr 4583] Sale Order lines - no stock Waring after "Save & New"

 

Public bug reported:

Hey ...

What you need before?
. some "Stockable Products" to test.
. create incoming product moves for those products

How to reproduce:
1. create a sale order
2. add a new sale order line
3. add one of the stockable product and use UoM +1 than real stock
4. the waring about availability comes up
5. press button "Save & New"
6. add another stockable product and also use UoM +1 than real stock
7. no more stock warning message will be displayed

Workaround:
. press button "Save & Close" instead of "Save & New" and add each line separately

Video demo: http://dl.dropbox.com/u/5636258/openerp-so-no-stock-
warning.ogv

This can be reproduced in webclient and GTK client.
This is tested on existing db's and new db's.

Thanks for fixing it
Thomas

** Affects: openobject-addons
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/784434

Title:
   [6.0.2 bzr 4583] Sale Order lines - no stock Waring after "Save &
  New"

Status in OpenERP Modules (addons):
  New

Bug description:
  Hey ...

  What you need before?
  . some "Stockable Products" to test.
  . create incoming product moves for those products

  How to reproduce:
  1. create a sale order
  2. add a new sale order line
  3. add one of the stockable product and use UoM +1 than real stock
  4. the waring about availability comes up
  5. press button "Save & New"
  6. add another stockable product and also use UoM +1 than real stock
  7. no more stock warning message will be displayed

  Workaround:
  . press button "Save & Close" instead of "Save & New" and add each line separately

  Video demo: http://dl.dropbox.com/u/5636258/openerp-so-no-stock-
  warning.ogv

  This can be reproduced in webclient and GTK client.
  This is tested on existing db's and new db's.

  Thanks for fixing it
  Thomas


Follow ups

References