c2c-oerpscenario team mailing list archive

["Rohan Nayani\(openerp\)" <711236@xxxxxxxxxxxxxxxxxx>]

Hello,

Thanks for Reporting.
It has been fixed in lp:~openerp-dev/openobject-addons/ron-dev-addons2
Revision ID: ron@xxxxxxxxxxx-20110202132437-zeetkjbnoqsb896g
Revision num:5136.

It will be available in trunk soon,


** Changed in: openobject-addons
       Status: In Progress => Fix Committed

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

Title:
  Task summary is not interpretable when Tasks are created from
  Manufacturing Order

Status in OpenERP Modules (addons):
  Fix Committed

Bug description:
  Hello,

  When Tasks are created from Manufacturing Order, the value 'Task
  summary' is not interpretable.

  You can check this issue using following example:

  step 1:

  Configure the product 'Maintenance Case' as like this:

  Procurement Type: Service
  Procurement Method: Make To Order
  Supply Method: Produce

  step 2:

  To create the BoM (Normal BoM) for the product 'Maintenance Case', configure two new product 'Application Engineer' 
  and 'Sr. Application Engineer' same as 'Maintenance Case' product. 

  step 3:

  Use these products - 'Application Engineer','Sr. Application Engineer'
  to create BoM for the product 'Maintenance Case'. (Add this BoM to
  create new Manufacturing Order)

  step 4:

  Now create Manufacturing order for the product 'Maintenance Case' and
  BoM which you have already configured for this product.

  Observation:

  Check the 'Task summary' field value of the Tasks which are generated
  from this Manufacturing Order(MO/00039) which is look like this
  :MO/00039::MO/00039.

  Actual Behavior:

  There are two tasks created corresponding to this Manufacturing
  Order(MO/00039) with same 'Task Summary' i.e. :MO/00039::MO/00039.

  So the problem is that I can't distinguish about which task is
  generated for which product among the BoM of the product 'Maintenance
  Case'

  Expected Behavior:

  Task is generated with interpretable 'Task Summary'(i.e.
  :MO/00039:Application Engineer and  :MO/00039:Sr. Application
  Engineer) like when the Task is created from Sale order for the
  product 'Application Engineer'(i.e. 'SO007:Application Engineer').

  Thanks..