odoo/odoo#170285
Created by fw-bot
Merged
at bd39917863a0cd5c30623acf97987be129a5c906
Statuses:
- legal/cla: Contributor License Agreement check
- ci/runbot: Odoo Test Suite
- ci/upgrade_enterprise: Test upgrades for enterprise master
- ci/template: Contact runbot team on discord for help.
- ci/style: Optional style check. Ignore it only if strictly necessary.
- ci/security: Required security check. Can only be ignored by security team.
- label
- odoo-dev:17.0-16.0-opw-3948817-mrp-fix-blocked-by-another-op-otd-e-53-fw
- head
- abea935472d5823ca6c34d2d966d12d252c58f08
- merged
- 1 year ago by Bugfix, Djamel Touati (otd)
| odoo/odoo | |
|---|---|
| 16.0 | #169417 |
| saas-16.3 | #169511 |
| 17.0 | #170285 |
| saas-17.1 | #171054 |
| saas-17.2 | #171185 |
| saas-17.3 | #171629 |
| 18.0 | |
| saas-18.1 | |
| saas-18.2 | |
| saas-18.3 | |
| saas-18.4 | |
| master | #171647 |
[FW][FIX] mrp: delete blocked_by_operation when changing bom in OP
Steps to reproduce the bug:
- Create a storable product “P1” with BoM - Operation: OP1, OP2 - OP2 blocked by OP1
- Navigate to Mrp > Configuration > Operations
- Select OP1 and select another BoM
- Return to the BoM of “P1”
Problem:
The OP2 is still linked to OP1, And a traceback when attempting to duplicate the BoM.
Solution:
Remove the link between OP2 and OP1