odoo/upgrade#5231
Created by Martin Maes (marm)
Blocked
- Merge method
- Review
-
CI
- ci/runbot: Test upgrades between stable versions
- ci/upgrade_enterprise: Test upgrades for enterprise master
- Linked pull requests
- label
- odoo-dev:master-mrp-custom_manufacturing-marm
- head
- 31a2cd407ec07d6f0356552e43dce9405bce6b35
| odoo/odoo | odoo/enterprise | odoo/upgrade | odoo/upgrade-util | |
|---|---|---|---|---|
| master | #129118 missing statuses missing r+ | #44384 missing statuses missing r+ | #5231 missing statuses missing r+ | #16 missing statuses missing r+ |
[IMP] mrp,mps/saas~16.5: added product configurator
Untill now, it was not possible to add/remove/modify any custom values from a manufacturing order, from mps, or from the inventory app.
The only way was to use the product configurator in the sales app, which made no sense as there could be manufacturing order creating a product with customs attribute without a sale order attached to it.
The goal in this pr is to reuse the sale_product_configurator, keeps its logic and make it available in other apps.
More related to this pr, product_variant_attributes was in fact a duplicate of product_template_attribute_value_ids from the new mixin that mrp.production inherits from.
odoo: odoo/odoo#129118
enterprise:odoo/enterprise#44384
> Warning Please follow and check the relevant boxes for your PR, otherwise the review may take longer.
For a PR that adds a new upgrade script (for the Odoo's master branch or one of the RR versions):
- [x] I've added the references to the Enterprise and/or Community PRs in the commit message, even if they are already merged.
- [x] I've added an overall description of the changes made in the Community/Enterprise branches.
For a PR that fixes an issue on an already existing upgrade script:
- [ ] I've added a clear description of the issue including information on how to reproduce it.
- [ ] I've tested the fix and included references of upgrade requests where this fix will be applicable in the form of upg-<request_number>.
- [ ] I've included references to the OPW, if applicable, in the form of opw-<ticket_number>.
- [ ] I've tested this fix on other DBs, not just the ones with the issue.
For all PRs:
- [x] My commit's title follows the right format.
- [x] My commit's body includes information about the changes.
- [x] I've added odoo/upgrade as a reviewer.
- [x] I've read and understood this list.
- [x] I will ensure all the CI checks are green.
> Note More info can be found in the wiki.