Tuesday, February 18, 2025
11 changes · 17.0
Resolved issues and error corrections
Mail command descriptions now use regular text styling instead of italic emphasis, preventing the ends of sentences from being visually cut off. This makes canned responses and channel command help text easier for users to read.
Original PR description
Purpose of this commit: The command descriptions (canned responses, channel command) currently use an italic font style due to being wrapped in the emphasis tag, causing the text to appear cropped at the end of the sentence. This commit resolves the issue by replacing the emphasis tag with a span tag. task-4485553 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Corrected a missing percent sign in the Spanish Mod 390 VAT report line label. This helps users read the report accurately and avoids confusion when reviewing annual VAT information.
Fixes the sample JavaScript provided in the Website HTML/CSS Editor so it works correctly after dialog changes. This prevents an error when users save the example and then enter edit mode, improving reliability for website customization.
Original PR description
Steps to reproduce: - In website, open the HTML/CSS Editor (Site > HTML/CSS Editor). - In the dropdown, select JS. - Uncomment the given example (about the "Hello World" dialog) and save. - Try to go in edit mode. => Traceback This happens since commit [1], which replaced the dialogs by OWL Dialog ones. Indeed, the call to `super` in the `init` function was forgotten, making the widget not being initialized correctly, and therefore not destroyed correctly either when going in edit mode. This commit adds this missing call. [1]: https://github.com/odoo/odoo/commit/57ed8bc0bf9d1ae2b7542d677a4d7e8fd1899ea2 opw-4243615
This fixes a website test so it uses the same default website that Odoo loads when multiple websites exist. It prevents false test failures in multi-website setups, especially when different websites use different themes.
Original PR description
To reproduce: Testing `test_ensure_correct_website_asset` with multiple website will consistently fail as the bundle from the biggest `website_id` is used whereas it compare the bundle to default website loaded, which looks to be the one with the smallest ID. Installing `test_themes` reproduce the issue consistently as the website with biggest and smallest ID will use different theme website with distinct bundle After this fix: As the website with smaller ID load by default, we use the smallest existing website_id rather than the biggest one rb-65788
The POS Sales Details report now rounds combined product quantities according to the product unit of measure. This prevents confusing decimal display errors, such as showing 74.60000000000001 instead of 74.6, and makes printed reports clearer and more reliable.
Original PR description
The Sales Details report in POS sometimes displays incorrect quantities due to floating point precision errors. This happens when summing product quantities that have decimal values, leading to…
The Sales Details report in POS sometimes displays incorrect quantities due to floating point precision errors. This happens when summing product quantities that have decimal values, leading to unintended rounding inaccuracies in the report output. Steps to Reproduce: 1. Create a sample product to be sold in POS. 2. Check the rounding precision set for the unit of measure for this product. 3. Open a new POS session and confirm an order with `14.9` quantities of the product. 4. Create another order for the same product, this time with `59.7` as the quantity. 5. Go to POS → Reporting → Sales Details, select the relevant POS, and print the report. 6. Issue: The generated PDF report incorrectly shows `74.60000000000001` instead of `74.6`. The sum of product quantities was not respecting the unit of measure's decimal precision, leading to floating point inaccuracies in the report. I Applied rounding to the quantity aggregation using the decimal precision of Product Unit of Measure, ensuring consistent and correctly formatted values in the report. opw-4430513 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix makes automated checks for the pivot view more reliable by waiting for downloads to finish before ending the test. It helps reduce random test failures, supporting smoother maintenance and more dependable release validation.
Original PR description
This commit fixes two pivot tests failing randomly by ensuring that we wait for the download to be completed before ending the test or asserting the steps. Runbot error-134572 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Timesheet reports now keep their columns aligned when users print only timesheets linked to helpdesk tickets. This ensures ticket-related entries display correctly and reports remain easy to read.
Original PR description
Steps to reproduce: - install helpdesk_timesheet - Go to `Timesheets` - Select ticket-linked timesheets only. - print report. Issue: - Tickets names are not rendered on the report, causing misalignment. Fix: If the column `timesheet_record_label` exists, render the cell anyway. task-4476391 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change adjusts internal performance tests for appointment features after a related access-rights update changed how publishing permissions are checked. It helps keep automated test expectations accurate when the website feature is installed, without changing the appointment behavior customers use.
Original PR description
Related to https://github.com/odoo/odoo/pull/195866. Now that `Can publish` is based on access rights, some extra queries are needed when `website` is installed. Note that the `appointment`-only and `appointment.hr`-only counts are unchanged. task-3175890
The Spanish Libro de IVA Excel export now places vendor bill references and reception numbers in the correct columns. This helps businesses produce more accurate VAT reporting files and reduces manual correction before submission or review.
Original PR description
This commit fix 2 columns in the Libro de IVA xlsx export file: 1. **expense_series_number**: before it was the move name, now it's the move ref 2. **reception_number**: before it was blank, now it's the move name task-4508992
The Knowledge app sidebar now resizes accurately for users working in right-to-left languages. This prevents the sidebar from moving incorrectly during resizing, improving usability for affected language settings.
Original PR description
Previously, in RTL mode, sidebar resizing calculations were incorrect, causing the sidebar to not follow the mouse properly resulted in incorrect resizing. This fix ensures accurate resizing behavior. Task-4571290
The cohort reporting tests were updated to wait for file downloads to finish before completing checks. This reduces random test failures, helping keep release validation stable without changing business features.
Original PR description
This commit fixes a cohort test failing randomly by ensuring that we wait for the download to be completed before ending the test or asserting the steps. Runbot error-134572