Friday, February 6, 2026
9 changes · 17.0
Resolved issues and error corrections
This update allows purchase users to delete incorrect line items when creating bills from purchase orders. Previously, users couldn't remove unwanted items, leading to inaccurate billing records. This change ensures purchase bills accurately reflect the ordered products, improving data integrity.
Original PR description
* Problem: when purchase user create bill from PO they only to record bill for some product not all so some move line need to be deleted, but no deleted button appear * Reason: Purchase User only have read, create, write access to journal items 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
This update fixes a problem where resending invoices through the Peppol network could incorrectly mark them as ‘skipped’. The change prevents users from repeatedly resending invoices in a ‘processing’ or ‘skipped’ state, ensuring accurate invoice tracking and delivery. This improves the reliability of our Peppol integration.
Original PR description
This fix addresses two issues related to resending invoices via Peppol. It prevents users from accidentally resending an invoice and having its status incorrectly set to “skipped”. It also prevents from resending an invoice via Peppol when it is already in a “processing”, then "skipped" state. Steps to reproduce: - Create and send a customer invoice to Peppol - Try to send it again, Odoo sets the status to “skipped” - Try to send it again, Odoo resends the invoice via Peppol This fix is a light adaptation of the `_is_applicable_to_move` method introduced in version 18. After the fix: Trying to resend to Peppol an invoice already in "processing" or "done" state is prevented. opw-5491341 Forward-Port-Of: odoo/odoo#247324
This update resolves an issue preventing users with restricted company access from reloading translations. The fix bypasses a privilege check during data retrieval, allowing the translation reload process to continue smoothly. This improves usability for users who don't have access to all company data.
Original PR description
When a user doesn't have access to all companies, he couldn't reload the translation terms. However, the exception occurs in the call to _get_chart_template_data, which doesn't especially require privileges, because it is static data. With this commit, we bypass the lack of company access to retrieve this data, and let the user continue the language reloading process. Task-id: [5916490](https://www.odoo.com/odoo/project.task/5916490)
This update ensures consistent styling for mentions across both small and full composer views. The change improves the visual presentation and addresses potential overflow issues, particularly on smaller devices, resulting in a cleaner and more user-friendly experience.
Original PR description
Use the same style in full composer than in small composer. Tweak style to account for small device, better handle overflows task-5916878 Before / After (small composer) <img width="342" height="466" alt="image" src="https://github.com/user-attachments/assets/234ff152-3c5a-4c82-b257-2800a752dd3a" /> <img width="496" height="476" alt="image" src="https://github.com/user-attachments/assets/60b3d12d-38ea-429a-9dec-441886ac022e" /> Before / After (full) <img width="413" height="394" alt="image" src="https://github.com/user-attachments/assets/c51e053f-7eb2-4ee0-8a9a-bd068ee9ded0" /> <img width="487" height="555" alt="image" src="https://github.com/user-attachments/assets/d0a3514d-aa1f-4d89-8fe4-7964ec20a288" />
This update fixes an issue where suggested mentions in the full composer weren't correctly sorted, preventing users from easily seeing followers at the top. The change ensures that mention suggestions are now properly sorted based on follower relationships, improving the composer's usability and efficiency. This resolves a minor inconvenience for users.
Original PR description
Fetch/sort suggestion in the full composer don't receive the thread param which leads to follower not being sorted at the top. task-5917226
This update removes the direct technical contact email address (peppol.iap@odoo.com) from the Peppol proxy, enhancing data security. Instead, the service name is now displayed, aligning with previous versions and simplifying client interactions. This change ensures our support information is presented in a more secure and consistent manner.
Original PR description
…pport Our TechnicalContactUrl is peppol.iap@odoo.com, it should not be exposed to the client as the support contact. Let's just expose the name of the service like we do above 18.0. task-none Forward-Port-Of: odoo/odoo#247607
This update corrects a technical issue within the account_edi_ubl_cii module that was incorrectly importing data related to vendor refunds. The change ensures that only the necessary financial information is processed, improving data accuracy and preventing potential errors in financial reporting. This resolves issues reported through internal tracking (opw-5870516, opw-5898302, opw-5917394, opw-5892671).
Original PR description
opw-5870516 opw-5898302 opw-5917394 opw-5892671
This update corrects a bug where the email address for Belgian company contacts was missing from VAT reports when an invoice address wasn't specified. The fix automatically pulls the email from the contact's parent record, ensuring accurate reporting and compliance. This prevents data discrepancies in exported XML reports.
Original PR description
**Steps to reproduce:** - Install l10n_be_reports and contacts - Switch to a Belgian company (e.g. BE Company CoA) - Go to Contacts - Open the company contact (i.e. BE Company CoA) - Add an invoice address withtout email - Create an invoice: * Customer: [a Belgian customer with a VAT number] * Invoice Lines: [a line with a tax] - Confirm the invoice - Go to "Accounting / Reporting / Belgium / Partner VAT Listing" - Export the XML **Issue:** In the XML, "<EmailAddress>" is empty althouth it is mandatory. **Cause:** The email is retrieved from the invoice address, but there is no fallback on the parent contact if it is empty. **Solution:** Fallback on the email of the parent contact as it is the case for the phone. opw-5870750
This update adjusts the taxonomy used for Dutch tax reports to the latest NT20 standard. This change ensures compliance with current Dutch tax regulations and maintains compatibility with older versions of the reporting templates. No new functionality was added.
Original PR description
The taxonomy for the Dutch tax reports was updated from NT19 to NT20. There were only changes in the namespaces. Olders versions of the XBRL template are kept for backwards compatibility. task-4568359