Wednesday, February 11, 2026
6 changes · 19.0
Enhancements to existing features
Users can now switch a posted invoice to a credit note, or the reverse, when its document sequence has been manually cleared. This removes an unnecessary blocker and avoids the need to export, delete, and re-import documents just to correct the type.
Original PR description
Previously, switching an Invoice to a Credit Note (or vice versa) on a posted in_()/out_() move raised a blocking error. This forced users to export, delete, and re-import the document with the correct move type. This **PR** relaxes the restriction for posted moves whose sequence has been manually cleared, allowing the `Switch Invoice/Credit Note` action to proceed in that specific case. **task**-5905206 Forward-Port-Of: odoo/odoo#247729 Forward-Port-Of: odoo/odoo#247349
Invoice line descriptions now appear automatically when users work with the product or description fields, removing the need to click a separate visibility toggle. This makes invoice entry smoother and reduces friction during day-to-day accounting work.
Original PR description
Currently, the Description field's visibility is controlled by a manual toggle icon when editing invoice lines with a product. This commit improves the user experience by automatically making the Description field visible when the user focuses on (or starts editing) either the Product field or the Description field itself. This is achieved using JavaScript focus and blur mechanisms to eliminate the need for manually clicking the '3-bar' visibility toggle. task-5385721 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Romanian eTransport reporting now records the XML sent for stock movements, making submitted shipment data easier to trace. The update also aligns reported product pricing and rounding with the required XML format, helping reduce reporting inconsistencies.
Original PR description
- Adding logging of sent XML into move chatter - Adjusting the XML generator to use standard unit price - Adding rounding for product values as required by the XML structure task-5892338 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#247919 Forward-Port-Of: odoo/odoo#247541
Editable content in the HTML editor is now marked so browser translation plugins do not automatically rewrite it. This helps prevent unintended translated text from being saved by auto-save, reducing accidental content changes for users.
Original PR description
Browser translation plugins were altering editable content by replacing the original content with translated versions, which caused issues when paired with auto-save. To prevent this behavior, the attribute `translate="no"` has been added to editable fields. task-5485078 Forward-Port-Of: odoo/odoo#247827
The Sign app now includes a Japanese-compatible font that can be selected for PDF generation. This helps prevent Japanese text entered in signature fields from appearing as unreadable boxes in downloaded documents.
Original PR description
When using the sign module, the chosen font when building the PDF defaults to 'Helvetica', which does not support languages that do not use ASCII characters. There is a system parameter…
When using the sign module, the chosen font when building the PDF defaults to 'Helvetica', which does not support languages that do not use ASCII characters. There is a system parameter 'sign.use_custom_font' which, when given a font name, will search /addons/web/static/fonts/sign for fonts. However, most languages have no supported fonts. Adding these fonts (.ttf) will allow users to enter them in 'sign.use_custom_font' and generate PDFs with new languages. Steps to Reproduce on Runbot Go to Sign Uplodad PDF Add text box Sign > Enter Japanese in text box Validate Download Result: Japanese will be replaced with boxes Possible Improvement: Instead of users manually entering unknown font names in system parameters, check the text when generating pdf and automatically fetch the needed font. Otherwise, how would users know how to place the correct font name in the specific parameter? opw-5899773 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
Company information enriched from Dun & Bradstreet is now shown in a dedicated chatter card instead of mixing industry tags into the partner Tags field. This keeps partner records cleaner while making key company details easier for users to review during communication.
Original PR description
Before: Industry tags coming from DnB were stored in the Tags section of res.partner. and there was no Company info card in chatter. After: Industry tags coming from DnB are not stored in the Tags section of res.partner. Company card is created in chatter that is having details from Dnb along with tags. task-5373200 Forward-Port-Of: odoo/odoo#239464