Wednesday, September 16, 2026
9 changes · 19.0
Resolved issues and error corrections
Long bill reference text in outstanding credits or debits is now shortened visually so it does not overflow the page. This keeps Credit Note and Vendor Bill screens readable and easier to use when references contain unusually long values.
Original PR description
The "Outstanding credits" or "Outstanding debits" sections of a Credit Note or Vendor Bill will overflow when the "Bill Reference" is too long. We resolve this by applying the text-truncate class. Steps to Reproduce: 1. Create a new 19.0 db and load demo data. 2. Accounting -> Vendors -> Refunds -> RBILL/2026/09/0001 3. Click the entry in the Outstanding credits section. 4. Enter a long "Bill Reference" value, e.g. asdf asdfasfasdfasdfasdfasdfasdfasdfasdfasdfasdf. 5. Go back to the Credit Note and observe the text overflow. opw-6558982 <img width="1254" height="1162" alt="bill_reference_long" src="https://github.com/user-attachments/assets/8c762b50-65a8-44bf-9a28-bd34887d5928" /> <img width="1620" height="1294" alt="overflow" src="https://github.com/user-attachments/assets/f5c47404-fb7f-4715-8815-cabe5dda3805" /> <img width="1586" height="1159" alt="truncated" src="https://github.com/user-attachments/assets/2a80f656-0a12-4805-9c1d-fd20379655ce" />
This fixes places where product quantity precision was still using an old internal name after a previous rename. It helps ensure point of sale, stock packaging, and Jordanian POS electronic invoicing use the intended number of decimals instead of defaulting to two.
Original PR description
…al.precision The `decimal.precision` "Product Unit of Measure" was renamed "Product Unit" in 18.1. Some occurences called the old name still exist in the code. This is silently fallbacking on the default 2 decimals from the `precision_get`. See: https://github.com/odoo/odoo/pull/193490 task-none
Long-pressing an order line in Point of Sale no longer resets a manually adjusted price back to the product's original price. This helps cashiers keep intended pricing changes intact and reduces checkout errors.
Original PR description
Long-pressing an order line recomputed its price and reset it to the product's original price. Preserve the existing price when the product is neither configurable nor part of a combo. --- Task: https://www.odoo.com/odoo/project/1737/tasks/6570304
This fix updates field service sales to use the renamed product unit precision setting. It helps ensure quantities are rounded with the intended accuracy instead of silently falling back to a default value.
Original PR description
The `decimal.precision` "Product Unit of Measure" was renamed "Product Unit" in 18.1. Some occurences called the old name still exist in the code. This is silently fallbacking on the default 2 decimals from the `precision_get`. See: https://github.com/odoo/odoo/pull/193490 task-none
Web Studio now correctly removes nearby text when a selected page structure element is deleted. This prevents leftover text from remaining in customized views, making Studio edits apply more reliably.
Original PR description
Have an arch like ``` <div> <br /> TEXT <span /> </div> ``` Now remove the block `TEXT <span />` Before this commit, the resulting inheriting arch was just `<xpath expr="//span" position="replace" />` So the `TEXT` was not removed After this commit, the `TEXT` is removed along with the following span opw-6524957
Point of Sale users can now remove the customer filter when viewing quotations or orders, even if a customer was selected beforehand. This makes it possible to see all available quotations and orders instead of being stuck with results for one customer.
Original PR description
When a customer was selected before opening the quotations/orders view, a default partner filter was applied. However, the partner was also added directly to the domain. Therefore, removing the partner filter from the search bar had no effect, as the domain continued to restrict the records to that partner. We now only use the default search filter so that users can remove it and display all available quotations/orders. --- Task: https://www.odoo.com/odoo/project/1737/tasks/6537521
Fixed an issue that caused an error when opening sales or purchase receipts from Invoice Analysis. This lets users review receipt details directly from analysis reports without interruption.
Original PR description
When enabling Sale/Purchase Receipts and trying to open the form view from Invoice Analysis, an error occurs. The issue is caused by the `move_type` used in `_where()`, which includes a type that is not defined in the `move_type` field selection. Steps to reproduce: - Enable Sale/Purchase Receipts. - Create a Sale/Purchase Receipt for partner A and confirm it - Go to Invoice Analysis and open the Pivot view - Click on a cell to open partner A's receipt, then try to open the form view - Error Ticket [link](https://www.odoo.com/odoo/project.task/6462153) opw-6462153 Forward-Port-Of: odoo/odoo#288077 Forward-Port-Of: odoo/odoo#282922
This fixes an issue in recruitment where creating a contact linked to an applicant could use the wrong information. It helps ensure applicant contact records are created with the intended details, improving data accuracy for hiring teams.
Original PR description
The values associated with the applicant's linked partner must be used during creation. Task-6479653 Forward-Port-Of: odoo/odoo#288023 Forward-Port-Of: odoo/odoo#287997
The backend printer test now tries to print directly on iMin printers before using the generic ePOS test flow. This helps businesses verify iMin point-of-sale printer setups more accurately while keeping the existing fallback if the device is unavailable or the test fails.
Original PR description
Before this PR:
=
- Clicking "Test" from the backend always follow generic ePOS test flow.
After this PR:
=
- The backend test first attempts to print a test receipt on iMin printer. If the printer is unavailable or the test fails, it falls back to the existing ePOS test flow.
task-6268687