Wednesday, February 4, 2026
12 changes · 18.0
Enhancements to existing features
This update adjusts a test case within the l10n_pe_edi module to reflect a recent change in how debit notes are processed through Peppol. This ensures the test case accurately validates the system's functionality after the Peppol update. The change was necessary to accommodate the addition of a new node during debit note creation.
Original PR description
A Node was added when creating debit notes in peppol, so the change was also applied to the debit note template to adjust a test case task-5875689
Resolved issues and error corrections
This update fixes a problem where automated tests relied on specific demo data, causing inconsistent results. The change ensures tests always use a consistent partner for searching, improving the reliability of our automated testing process. This enhances the overall stability and predictability of our website sales functionality.
Original PR description
As part of the forward part for [1] the shop mail tour was updated because the new demo partner was earlier alphabetically than the partner generated for the test, and tests run with demo data for CI in this version. The test should create a partner that will appear first in the m2o selection regardless of whether demo data is installed. [1]: 549708965924b17403ef7c8e6a6d5bc43af460c3 runbot-238406 Forward-Port-Of: odoo/odoo#245753
Documentation and clarification updates
This pull request updates our contributor agreement to include a new contributor from Aerospacelab. This ensures proper legal recognition and allows Aerospacelab to contribute to the Odoo project according to our guidelines. It's a standard process for onboarding new developers.
Original PR description
https://github.com/odoo/enterprise/pull/105990 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves a test failure in the restaurant POS booking process. The fix replaces a method used for general loading with one specifically designed to wait for RPC requests, ensuring the tour accurately reflects the system's behavior when booking and releasing tables. This improves the reliability of the test and the overall booking experience.
Original PR description
Fix failing tour `test_book_and_release_table` by replacing `waitForLoading`, which is intended for POS loading, with `waitRequest` to properly wait for RPC requests. Error-227652 Task-5897383
This update fixes an issue where vendor bill labels on payable lines were not correctly populated when the Payment Reference was empty. Now, the payable line label automatically displays the Bill Reference when no Payment Reference is provided, and updates accordingly when the Payment Reference is changed. This ensures accurate labeling of vendor bills for better reporting and reconciliation.
Original PR description
Before PR: - On vendor bills and refunds, if the Payment Reference is empty, a placeholder saying `Use Bill Reference` is shown. But the Bill reference is still not written on the Payable line, making the label empty. - When Payment Reference is set, updating the Payment Reference does not update the payable line label. After PR: - The payable line label is now populated with the Bill Reference when the Payment Reference is empty. - Now, when Payment Reference is set, updating the Payment Reference updates the payable line label. - Modified the test cases which were failing due to an empty label. Related PR (Enterprise) : https://github.com/odoo/enterprise/pull/91535 Task : 4982864
This update replaces the SFU (Server-Side File Upload) bundle with version 1.3.3, addressing a technical update to improve the performance and stability of file uploads within Odoo. This change ensures continued optimal functionality for users uploading and managing files.
Original PR description
https://github.com/odoo/sfu/releases/tag/v1.3.3 Forward-Port-Of: odoo/odoo#244971
This update resolves an issue where the POS ID wasn't being correctly transmitted to the blackbox during v1 CleanCash integration. The fix ensures accurate data transmission, improving the reliability of the fiscal data reporting process. Additionally, a security enhancement restricts blackbox device selection to the Fiscal Data Module in POS configuration settings.
Original PR description
When using a v1 CleanCash blackbox, the command being sent to the blackbox was mistakenly sending a POS ID of " ". It just so happened this worked correctly when testing with our blackbox because it had " " registered as a POS ID. The POS ID is now sent correctly. Another small fix was made to only allow selecting blackbox devices in the Fiscal Data Module field in the POS config settings. task-5077448
This update resolves an issue where tickets in 'folded' (closed) stages were incorrectly displayed in the helpdesk email plugin. The fix ensures that closed tickets are filtered out, preventing them from appearing in the plugin's results and improving the user experience. This ensures users only see active tickets.
Original PR description
**Steps to reproduce:** - Install Mail_plugin - Setup the outlook mail plugin in Outlook - Once connected, click on a mail from a contact on the database - Click on the Odoo Inbox Addin. action - Under the contact 5 related tickets are showed - Create 5 tickets with priority and put them in folded stage (closed) - Create new normal tickets - User can't see new tickets in the plugin **Issue:** The search is done on priority and then id ordering, this means that tickets in folded stages (closed) which have a high priority are always showed first. Tickets in a folded stage are considered as closed, so they should not appear anymore in the contact data to avoid displaying them indefintely. **Fix:** Adapted search domain and removed fold attribute in the answer. opw-5075477
This update resolves a problem with Indian GST reports where test cases were failing due to a recent change in how payable lines are labeled. The test cases have been updated to now correctly account for the new label format that includes the bill reference, ensuring accurate reporting.
Original PR description
Before: - Test cases in Indian GST reports were failing because they expected payable line labels like `installment #1`, but after the community fix (Task: 4982864), payable lines are now populated with the bill reference when Payment Reference is empty, resulting in labels like `TEST/0001 installment #1`. After: - Modified test cases to expect the new label format that includes the bill reference. Related PR (Community) : https://github.com/odoo/odoo/pull/221491 Task: 4982864
A bug was causing incorrect order quantities to be sent to the kitchen when using the numpad in the POS Restaurant Preparation Display module. This was resolved by adding a brief delay to ensure the quantity is updated before the order is submitted, preventing errors in the kitchen display.
Original PR description
TASK: [#5897381](https://www.odoo.com/odoo/project/1737/tasks/5897381) --- Inside tour tests environment for POS Restaurant Preparation Display module, when using the numpad to change the quantity of a product in the POS and sending the order to the kitchen immediately after, there is a chance that the quantity is not updated in time. This could lead to sending an order with an incorrect quantity to the kitchen display. As a result, the test `test_payment_does_not_cancel_display_orders` was failing. We add a small delay after using the numpad to ensure the quantity is updated before sending the order.
This update resolves an issue where products with a zero price were being sent to UrbanPiper during menu synchronization, causing problems on their end. The change now excludes these zero-price products from the sync process, ensuring smoother integration with UrbanPiper and preventing potential errors.
Original PR description
Before this commit: --- - During menu sync, charge products with a price of zero were sent to UrbanPiper which caused issues on the UrbanPiper side. After this commit: --- - Exclude charge products with a zero price from the menu sync. task-5867272
This update fixes an issue in the French P&L report where accounts 65 were incorrectly categorized. The accounts have been moved to the 'Other Expenses' line, ensuring accurate financial reporting and alignment with French accounting standards. This improves the clarity and reliability of the financial data.
Original PR description
On the french P&L, accounts 65 are refferenced in the line 'Other purchases and external charges' but this is not where those accounts need to be, they need to be part of the line 'Other Expenses' task-5446018 Forward-Port-Of: odoo/enterprise#103357