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

Bug #1253701 reported by Pedro Manuel Baeza
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Won't Fix
Wishlist
OpenERP R&D Addons Team 2
OpenERP Community Backports (Addons)
Status tracked in 7.0
6.1
Fix Released
Undecided
Unassigned
7.0
Fix Released
Undecided
Unassigned

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.

Related branches

summary: - Incorrect multi-company rule for BOMs
+ [trunk/7.0/6.1/6.0] Incorrect multi-company rule for BOMs
Revision history for this message
Pedro Manuel Baeza (pedro.baeza) wrote :

I have put it on the noupdate=0 section to allow existing users to get updated the rule definition.

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
Martin Trigaux (OpenERP) (mat-openerp) wrote :

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
status: Confirmed → Won't Fix
Revision history for this message
Pedro Manuel Baeza (pedro.baeza) wrote :

Hi, Martin, I think you have to reconsider your opinion because:

- Current behaviour is not consistent: product multi-company rule allow this while BoM doesn't.
- This is not a feature request if you consider that this modification allow that consistency and the system must ensure correct defaults.

There's no problem to include the rule on noupdate section if this is a blocking point.

Regards.

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.