Skip to content

17.0#1

Open
drzaphod85 wants to merge 2803 commits intodrzaphod85:17.0from
OCA:17.0
Open

17.0#1
drzaphod85 wants to merge 2803 commits intodrzaphod85:17.0from
OCA:17.0

Conversation

@drzaphod85
Copy link
Copy Markdown
Owner

No description provided.

OCA-git-bot and others added 30 commits October 6, 2025 07:37
Signed-off-by rousseldenis
Fixes portal template incorrect rendering of discounted unit prices
Signed-off-by rousseldenis
Signed-off-by rousseldenis
When a blank SO is created and then a product line is added, the carrier should also be set.
This is because the carrier is not set on create when there are no product line.
Signed-off-by HaraldPanten
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: sale-workflow-17.0/sale-workflow-17.0-sale_order_carrier_auto_assign
Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-17-0/sale-workflow-17-0-sale_order_carrier_auto_assign/
Currently translated at 100.0% (10 of 10 strings)

Translation: sale-workflow-17.0/sale-workflow-17.0-sale_order_carrier_auto_assign
Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-17-0/sale-workflow-17-0-sale_order_carrier_auto_assign/it/
Signed-off-by rousseldenis
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: sale-workflow-17.0/sale-workflow-17.0-sale_delivery_state
Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-17-0/sale-workflow-17-0-sale_delivery_state/
This module simplifies and emphasizes the usage of packaging in sales orders.

- Packaging fields in sale order lines appear before product quantity fields.
- When selecting a product to sell, its default packaging is added automatically.

Why is this module useful? Packaging usage in Odoo is designed to be computed
automatically when you choose the final amount of products to sell. Although
you can still do that, with this module the natural usage is inverted: it's
easier for you to select the packaging and quantity first, and then the final
amount of products is computed automatically.

@moduon MT-3695
Currently translated at 100.0% (4 of 4 strings)

Translation: sale-workflow-16.0/sale-workflow-16.0-sale_packaging_default
Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-16-0/sale-workflow-16-0-sale_packaging_default/es/
When creating SO from mobile view or from "Commercial Quotations" menu installed by `sale_order_product_picker`, the pop-up form view that appears when clicking on the line kanban kard didn't have the fields in the correct order.

@moduon MT-3930
…ckaging

Before this patch, we had this problem:

1. Add new SO line.
2. Set a packaging and a packaging qty. The UoM qty is computed. Good.
3. Set UoM qty to zero. Packaging and packaging qty remain with previous value. Bad.

When user sets UoM to zero, Odoo should remove any packaging information.

Notice that, when adding a new line, that qty will be zero at the beginning, but we will want to still get the defaults. Thus, this change is only applied when the user *is* actually setting that value, and not on any other circumstance. I needed to override the `onchange()` method to propagate that information.

@moduon MT-3930
OCA-git-bot and others added 30 commits March 1, 2026 22:33
Signed-off-by pedrobaeza
With the current order, the super to _track_template from the mixin was never called.
Which was a good thing since it was also buggy;
however the override in this model was removed on the assumption that it was.
Signed-off-by StefanRijnhart
Signed-off-by pedrobaeza
Previously, if no context is provided, the code calls to super to
continue getting prices, but that's not a proper default behavior, as
in that case, the super code never mark the rule as not applicable, as
all the comparisons are not met.

We fix that not calling super if the rule type is a global one, but
providing a defaul dictionary for not crashing, although the quantity
comparisons were not accumulated, and thus, the rule may not match if
a minimum comparison is provided.

TT61419
…nt computation

As the price computation is done in 2 steps, first with the pricelist
item, and then the unit price/discount, if the pricelists are set in
several levels, the first step only computes the direct rule, but if the
global rule is at another pricelist, then on the final unit price
computation, the cumulative quantities are not set in the context, so we
need to inject the context as well in this compute.

TT61419
Signed-off-by pedrobaeza
Signed-off-by rousseldenis
…ake the sale_product_configurator and web_widget_product_label_section_and_note modules compatible.
Signed-off-by rousseldenis
Signed-off-by pedrobaeza
Signed-off-by pedrobaeza
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: sale-workflow-17.0/sale-workflow-17.0-sale_payment_sheet
Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-17-0/sale-workflow-17-0-sale_payment_sheet/
Signed-off-by Shide
Currently translated at 100.0% (97 of 97 strings)

Translation: sale-workflow-17.0/sale-workflow-17.0-sale_payment_sheet
Translate-URL: https://translation.odoo-community.org/projects/sale-workflow-17-0/sale-workflow-17-0-sale_payment_sheet/it/
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.