Monday, June 9, 2025
8 changes · saas-18.3
Enhancements to existing features
The web interface now allows currencies to be refreshed manually through the existing currency service. This gives teams more control over when currency data is reloaded, helping keep financial displays up to date when needed.
Original PR description
This commit will add the possibility to call reloadCurrency function from the service. task-4749335 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Before this commit, when the user is in debug mode and go to the form view of a task with some timesheets, he can optionally display the view button in the sub list view of timesheets. The problem is the view button will return the first form view found in timesheet model. Since timesheet model is in fact `account.analytic.line`, the first form view opened is the one used for Analytic Items and not for the timesheets. This commit alters the form view by using `form_view_ref` context key on ti
Original PR description
Before this commit, when the user is in debug mode and go to the form view of a task with some timesheets, he can optionally display the view button in the sub list view of timesheets. The problem is the view button will return the first form view found in timesheet model. Since timesheet model is in fact `account.analytic.line`, the first form view opened is the one used for Analytic Items and not for the timesheets. This commit alters the form view by using `form_view_ref` context key on timesheet_ids field to be able to load the expected form view. task-4781729 Forward-Port-Of: odoo/odoo#209653
*: sale_stock Issue: ====================== The forecast availability(icon) on the sales order incorrectly appears red even when enough stock is available for products in multi-step deliveries. Steps to Reproduce: ====================== 1. install sale_management & stock module. 2. Activate multi-step delivery in the warehouse. 3. Sell a product that has sufficient stock. 4. Ensure that enough quantities are reserved on the created picking. 5. Check the forecast availability(icon)
Original PR description
*: sale_stock Issue: ====================== The forecast availability(icon) on the sales order incorrectly appears red even when enough stock is available for products in multi-step deliveries. Steps…
*: sale_stock Issue: ====================== The forecast availability(icon) on the sales order incorrectly appears red even when enough stock is available for products in multi-step deliveries. Steps to Reproduce: ====================== 1. install sale_management & stock module. 2. Activate multi-step delivery in the warehouse. 3. Sell a product that has sufficient stock. 4. Ensure that enough quantities are reserved on the created picking. 5. Check the forecast availability(icon) on the sale order. Issue: ====================== The 'is_consuming' method is not considered for internal transfer moves during forecast availability computation. This leads to incorrectly flagging the forecast icon as red on the Sales Order, even when sufficient stock is available and reserved. With this commit: ====================== This fix ensures that the forecast icon correctly reflects stock availability by considering internal transfers in a multi-step delivery. the icon currently appears green on the Sales Order when there is enough stock to fulfill the demand. task - [4555666](https://www.odoo.com/odoo/project/966/tasks/4555666) Forward-Port-Of: odoo/odoo#199027
If the `End Date` is already defined and the user removes that date in the form view of productivity losses, an error is generated. Steps to reproduce: --- - Install the `mrp` module - Manufacturing > Configuration > Work Centers > Open any of the Work Centers - In the form view of Work Center, click on the `Lost` stat button - Open a new Productivity Loss form, set a future date in `End Date`, click elsewhere, then clear the `End Date` Traceback: --- `TypeError: unsupported operand
Original PR description
If the `End Date` is already defined and the user removes that date in the form view of productivity losses, an error is generated. Steps to reproduce: --- - Install the `mrp` module - Manufacturing > Configuration > Work Centers > Open any of the Work Centers - In the form view of Work Center, click on the `Lost` stat button - Open a new Productivity Loss form, set a future date in `End Date`, click elsewhere, then clear the `End Date` Traceback: --- `TypeError: unsupported operand type(s) for -: 'bool' and 'datetime.timedelta'` If the end date is missing, we will return from the method sentry-6641245276 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#212204
### Description of the issue/feature this PR addresses: - When pasting formatted content (like `<strong>` or `<font>`) into a region that already had same formatting, it caused nested identical tags, leading to exaggerated styling (e.g., "double bold"). ```html <!-- User pastes <strong>text</strong> inside <strong> --> <p><strong>text []</strong></p> <!-- Resulting HTML --> <p><strong>text <strong>text</strong>[]</strong></p> ``` ### Desired behavior after PR is merged: - Prev
Original PR description
### Description of the issue/feature this PR addresses: - When pasting formatted content (like `<strong>` or `<font>`) into a region that already had same formatting, it caused nested identical tags, leading to exaggerated styling (e.g., "double bold"). ```html <!-- User pastes <strong>text</strong> inside <strong> --> <p><strong>text []</strong></p> <!-- Resulting HTML --> <p><strong>text <strong>text</strong>[]</strong></p> ``` ### Desired behavior after PR is merged: - Prevents unwanted style amplification by unwrapping nested identical formatting tags. ```html <!-- Resulting HTML --> <p><strong>text text[]</strong></p> ``` task-4715409 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#213231 Forward-Port-Of: odoo/odoo#206258
Description of the issue this PR addresses: - Trailing zeros in tab width styles cause test mismatches with browser-normalized values. Current behavior before PR: - Tests may use widths like "24.0px" which differ from browser output "24px". Desired behavior after PR is merged: - Tab widths use Number() conversion to match browser formatting and avoid test mismatches. task-4853029 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Por
Original PR description
Description of the issue this PR addresses: - Trailing zeros in tab width styles cause test mismatches with browser-normalized values. Current behavior before PR: - Tests may use widths like "24.0px" which differ from browser output "24px". Desired behavior after PR is merged: - Tab widths use Number() conversion to match browser formatting and avoid test mismatches. task-4853029 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#213313
Following this commit : ==== - An online/offline toggle option is provided for the food delivery dropdown. - If the user has configured more than one provider and wishes to close/off one of the aggregator, then without going on the backend from the UI itself, the user can offline that particular provider and vice versa. task-4582032 Forward-Port-Of: odoo/enterprise#86813 Forward-Port-Of: odoo/enterprise#80333
Original PR description
Following this commit : ==== - An online/offline toggle option is provided for the food delivery dropdown. - If the user has configured more than one provider and wishes to close/off one of the aggregator, then without going on the backend from the UI itself, the user can offline that particular provider and vice versa. task-4582032 Forward-Port-Of: odoo/enterprise#86813 Forward-Port-Of: odoo/enterprise#80333
The aim of this commit is to provide a NIS code mapping for every country created by default in Odoo. Before this commit: If a 281.50 was created for someone in one of these countries, it would miss the `f2112_buitenlandspostnummer` field in the xml file resulting in the administration rejecting the file. After this commit: A pragmatic completion is made for those countries in `f2112_buitenlandspostnummer`. task: None Forward-Port-Of: odoo/enterprise#87081
Original PR description
The aim of this commit is to provide a NIS code mapping for every country created by default in Odoo. Before this commit: If a 281.50 was created for someone in one of these countries, it would miss the `f2112_buitenlandspostnummer` field in the xml file resulting in the administration rejecting the file. After this commit: A pragmatic completion is made for those countries in `f2112_buitenlandspostnummer`. task: None Forward-Port-Of: odoo/enterprise#87081