[trunk/7.0/6.1/6.0] Incorrect multi-company rule for BOMs
Bug #1253701 reported by
Pedro Manuel Baeza
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:
['|','|
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:
['|',('
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
lp:~pedro.baeza/openobject-addons/7.0-bug-1253701
Rejected
for merging
into
lp:openobject-addons/7.0
- Martin Trigaux (OpenERP) (community): Disapprove
- Raphaël Valyi - http://www.akretion.com (community): Approve
-
Diff: 31 lines (+7/-7)1 file modifiedmrp/security/mrp_security.xml (+7/-7)
lp:~pedro.baeza/ocb-addons/7.0-bug-1253701
- Holger Brunn (Therp): Approve (code review)
- Stefan Rijnhart (Opener): Approve
- Raphaël Valyi - http://www.akretion.com: Approve
-
Diff: 12 lines (+1/-1)1 file modifiedmrp/security/mrp_security.xml (+1/-1)
lp:~pedro.baeza/ocb-addons/6.1-bug-1253701
- Holger Brunn (Therp): Approve (code review)
- Stefan Rijnhart (Opener): Approve
- Omar (Pexego): Approve
- Raphaël Valyi - http://www.akretion.com: Approve
-
Diff: 12 lines (+1/-1)1 file modifiedmrp/security/mrp_security.xml (+1/-1)
summary: |
- Incorrect multi-company rule for BOMs + [trunk/7.0/6.1/6.0] Incorrect multi-company rule for BOMs |
Changed in openobject-addons: | |
assignee: | nobody → OpenERP R&D Addons Team 2 (openerp-dev-addons2) |
importance: | Undecided → Medium |
status: | New → Confirmed |
To post a comment you must log in.
I have put it on the noupdate=0 section to allow existing users to get updated the rule definition.