openerp-community-reviewer team mailing list archive

["Martin Trigaux \(OpenERP\)" <mat@xxxxxxxxxxx>]

Hello,

Thanks for the proposal but this more a feature request than a bug. How
you share boms depends on the company and people can adapt the rules if
they have different behaviour. We have no reason to change the current
one as it may satisfy current users.

Also as discussed on the ocb merge proposal, we should keep rules in
noupdate=1 parts.

Regards

** Changed in: openobject-addons
   Importance: Medium => Wishlist

** Changed in: openobject-addons
       Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of OpenERP
Community Backports Team, which is subscribed to OpenERP Community
Backports (Addons).
https://bugs.launchpad.net/bugs/1253701

Title:
  [trunk/7.0/6.1/6.0] Incorrect multi-company rule for BOMs

Status in OpenERP Community Backports (Addons):
  Fix Committed
Status in OpenERP Community Backports (Addons) 6.1 series:
  Fix Committed
Status in OpenERP Community Backports (Addons) 7.0 series:
  Fix Committed
Status in OpenERP Addons (modules):
  Won't Fix

Bug description:
  Products multi-company rule is:

  ['|','|',('company_id.child_ids','child_of',[user.company_id.id]),('company_id','child_of',[user.company_id.id]),('company_id','=',False)]

  that allows to assign a product to a parent company and let its
  children companies to see this product.

  However, multi-company rule for BOMs is:

  ['|',('company_id','child_of',[user.company_id.id]),('company_id','=',False)]

  that only allows down to top permissions, which is incoherent and
  doesn't meet real requirements for a lot of companies.

  I propose then to change this rule to the same as the one for product.

  Thank you.

  Regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ocb-addons/+bug/1253701/+subscriptions