[trunk/7.0] Internal move name not set properly

Bug #1094832 reported by Bertrand Rétif
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Fix Committed
Medium
OpenERP R&D Addons Team 2

Bug Description

Hello,

When you want to create internal move, the name of the move are not properly set in 7.0
The name is blank

Steps to reproduce the bug:
---------------------------
- Create a new db with demo data
- Install module:
  - Sales management
  - Warehouse
- Choose France accounting and all other options by default
- Put admin user in extended view (Technical Features")
- In warehouse configuration select:
  - Manage multiple locations and warehouses
- Go to Warehouse -> Configuration -> Location, select Output location
 - Edit chained location customer: Set "Chaining type" to "Manual operation"
- Confirm sale order SO006.
- Run schedulers
   - A new internal move is generated but with no reference. (INT/XXXX is missing)

I attached a patch to fix this issue in stock/stock.py file

Do not hesitate to request any further details if needed.
Bertrand

Revision history for this message
Bertrand Rétif (bretif) wrote :
Amit Parik (amit-parik)
summary: - [7.0] Internal move name not set properly
+ [trunk/7.0] Internal move name not set properly
Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 2 (openerp-dev-addons2)
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Randhir Mayatra (OpenERP) (rma-openerp) wrote :

Hello,
This is issue is already fixed in branch lp: https://code.launchpad.net/~openerp-dev/openobject-addons/trunk-improve_addons30

  Revno : 8271

Changed in openobject-addons:
status: Confirmed → Fix Committed
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.