Monday, June 23, 2025
8 changes · 18.0
Resolved issues and error corrections
CSV imports of tax descriptions now preserve plain text without adding unwanted paragraph formatting. This keeps tax description data consistent and avoids small display or content changes caused by automatic HTML cleanup.
Original PR description
Before this commit, when plain text (e.g., "Some tax") was imported from a CSV file into the HTML field `description`, the system wrapped it in a `<p>` tag during normalization via `html_normalize`, since plain text is not valid HTML. After this commit, we add a check before record creation: - If the value is plain text without any HTML, we wrap it in a `<div>` to make it valid HTML. - If it already contains HTML, we leave it untouched. This avoids unintended `<p>` wrapping by `html_normalize`. Note: if content is wrapped in a `<div>`, `html_normalize` will strip it out. This ensures consistent HTML formatting for the description field during create/write operations and prevents unexpected automatic wrapping by the system. task-4862728
This fix prevents checkout warnings when a customer's stored name contains trailing spaces, such as after an import. It also helps imported text fields stay clean by trimming unnecessary spaces when configured, reducing avoidable data quality issues.
Original PR description
**Steps to reproduce:** 1. Install the website_sale app. 2. Import a user with trailing spaces in the Name field. 3. Make this user Admin in settings 4. Log in with that user and go to Website >…
**Steps to reproduce:** 1. Install the website_sale app. 2. Import a user with trailing spaces in the Name field. 3. Make this user Admin in settings 4. Log in with that user and go to Website > Shop. 5. Click on new and create a new product 6. Add this product to the cart and proceed to checkout. 7. The checkout form pre-fills the name (with trailing spaces). 8. fill other fields 9. Submitting the form triggers a warning due to changed name. **Expected behaviour:** - Name is not changed by us so it should let us checkout - There should not be trailing spaces in imported char fields if trim attribute is true **Issue:** - The name field from the form is trimmed in post request, but the value from the database (with trailing spaces) is used during comparison This results in a false positive change detection. - User's name with trailing spaces is because of Imported records does not check for trim attribute in backend but this is handled in ui. **Solution:** - Trim the database value before comparing it to the form input - Trim the values of char field before importing if trim attribute is true opw-4794220
This fixes who can see the task count on project milestones so it follows the intended access group. It helps ensure project information is shown consistently to the right users without changing milestone functionality.
Original PR description
fix in version-18.0
This fixes an issue in Discuss calls where peer offer filtering was silently skipped because the app referenced the wrong internal store. The change helps call connection handling behave as intended without introducing visible workflow changes for users.
Original PR description
Before this commit, peer offer filtering was not working as the reference to the store was incorrect. This wouldn't cause tracebacks or known connection issues as the error was caught and the filter was just ignored.
CIS report values for materials and payments are now rounded down, as required by UK government guidance. This helps ensure submitted report figures match compliance rules and avoids small rounding discrepancies.
Original PR description
Before, a fix was done to round column for materials and payments columns but the method was HALF-UP. This should always be DOWN as specified here https://assets.publishing.service.gov.uk/media/5d53df0040f0b6098ead46c2/cis-qsbvr-v2.2.pdf page 28 task-4881298
Urban Piper receipts now show the delivery identifier clearly in the receipt header when printed. This prevents staff from missing or misreading order delivery references due to overly light text.
Original PR description
- When printing urban piper receipt the delivery identifier was not correctly rendered in the receipt header. - This is caused by the `text-muted` class on the element, which is causing the text to be too light to be correctly printed. task-id: 4881459
Task planned dates now display in a consistent MM/DD/YYYY format, including leading zeros for single-digit months and days. This makes deadlines easier to read and aligns the project task list with expected date formatting.
Original PR description
Step to reproduce: - install project_enterprise - open project -> open a task - add a deadline (start and end date) - return to my task - Observe the date format for tasks with Planned Date → Dates do not include leading zeros for single-digit days or months. Issue: The view uses the `condensed="True"` attribute on the daterange widget, which removes zero-padding from the date format. Fix: Remove the `condensed` attribute Before:  After:  opw-4844618
A payroll expense test setup was adjusted so reconciliation checks focus on the intended accounting entry. This helps prevent misleading test results and supports more reliable payroll expense handling after recent accounting changes.
Original PR description
This commit removes the default account set in the setup of test_payroll_expense. Because of 67b5fc47ca4aa1abb60f198a87d7784ef400f796 the filter in get_all_amls_to_be_reconciled would get multiples amls instead of only one. community pr: https://github.com/odoo/odoo/pull/211443 opw-4751270