← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 740762] Re: [6.0.1] stock_move done date not recorded

 

Thanks for Reporting.

** Changed in: openobject-addons
   Importance: Undecided => Low

** Changed in: openobject-addons
       Status: New => Confirmed

** Changed in: openobject-addons
     Assignee: (unassigned) => OpenERP R&D Addons Team 2 (openerp-dev-addons2)

** Summary changed:

- [6.0.1] stock_move done date not recorded
+ stock_move done date not recorded

-- 
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/740762

Title:
  stock_move done date not recorded

Status in OpenERP Modules (addons):
  Confirmed

Bug description:
  Version: 6.0.1

  Module: stock
  Source: stock.py
  Class: stock_move
  Def: action_done

  When a stock_move is moved to done state the done date is not
  recorded. The code to update the move references the field
  stock_move.date_planned. However, stock_move doesn't have a
  date_planned field (I think this field existed in v5). The code (line
  2141) is:

  self.write(cr, uid, move_ids, {'state': 'done', 'date_planned':
  time.strftime('%Y-%m-%d %H:%M:%S')}, context=context)

  Based on the stock_move fields' descriptions I think the code should
  be:

  self.write(cr, uid, move_ids, {'state': 'done', 'date':
  time.strftime('%Y-%m-%d %H:%M:%S')}, context=context)

  
  Jeroen



References