Friday, October 31, 2025
9 changes · saas-18.3
Resolved issues and error corrections
The mail app’s automated test for searching discussion sub-channels now waits for the page state to settle before scrolling. This reduces false test failures under heavy system load and helps keep releases stable without changing end-user behavior.
Original PR description
The `test_discuss_sub_channel_search` tour ensures that lazy loading of threads works correctly with the search feature. Technically, the component uses the `useVisible` hook which waits for a trigger to be visible before loading more threads. However, under high CPU load, the `IntersectionObserver` might not detect the change. For example, clearing the search input will make the element disappear, but scrolling afterward may make it reappear. As a result, the component might not detect that it should load more threads. In practice, this should never happen. The test now waits for the state to update before scrolling. fixes runbot-181951 Forward-Port-Of: odoo/odoo#233419
The time off request form now only shows the document attachment field when supporting documents are enabled for that time off type. This prevents employees from seeing or using an irrelevant upload option and keeps the request process aligned with company configuration.
Original PR description
issue: - Field to attach documents is always visible when applying for time off regardless of whether we have allowed supporting documents in "time off types" or not <img width="641" height="505" alt="image" src="https://github.com/user-attachments/assets/0ec26822-5284-474f-b791-4b2b8e5eb9cc" /> <img width="511" height="265" alt="image" src="https://github.com/user-attachments/assets/ea546067-ac62-4e25-9a70-bbd86c053109" /> cause: - In commit [1], there was a change, which resulted to this issue [1] https://github.com/odoo/odoo/commit/944c11e61abead4f5157a7a7cb7b1f536bc14411 fix: - `supported_attachment_ids` now also depends on whether uploading files in a time off is supported or not opw-5144399 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When a cashier loads a sales order in Point of Sale and cancels the lot selection prompt, the system now leaves the order line unchanged. This prevents incorrect lot information from being added accidentally, improving order accuracy for tracked products.
Original PR description
Before this commit, when loading a sale order containing an order line tracked by lot, the system prompted the user to select a lot. However, even if the user canceled the selection, the lot was still added to the order line. After this commit, the lot will no longer be set if the user cancels the selection. opw-5162487 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#233281
The printed approval request report now displays labels and field values with better spacing and more consistent text sizing. This makes approval request documents easier to read and more professional when printed or shared.
Original PR description
Steps to Reproduce: - Install approvals module. - Navigate to Approvals → My Approvals → My Requests → Print report. Issue: - The formatting of the report is not proper. Solution: - Fixed the report's QWeb template (approvals.report_aprroval_request_document). - changed col-2 to col-3 to give the labels more space and improve alignment with the field values - changed h5 to h6 for more consistent and appropriate font size throughout the document **before :** <img width="777" height="818" alt="image" src="https://github.com/user-attachments/assets/86cbaf50-191a-412b-9b8e-149442256819" /> **after :** <img width="829" height="623" alt="image" src="https://github.com/user-attachments/assets/da237a87-7a7b-45db-8347-d64e1e987469" /> Forward-Port-Of: odoo/enterprise#95609
Archived bank account records are now ignored when checking whether multiple contacts share the same bank account. This prevents unnecessary warning banners on contact pages when the only matching bank account has already been archived.
Original PR description
If a res_partner_bank record shares an acc_number with other res_partner_bank records, even archived ones, the field duplicate_bank_partner_ids still includes partners from those archived records. As…
If a res_partner_bank record shares an acc_number with other res_partner_bank records, even archived ones, the field duplicate_bank_partner_ids still includes partners from those archived records. As a result, the contact page shows a banner indicating other partners use the same bank account, even though those res_partner_bank records have been archived. Steps to reproduce the issue: 1. Create a new bank account which has the same bank account number as another bank account already associated to a partner 2. Assign this new bank account to another partner 3. Archive this new bank account 4. Go to the contact page of the partner (from step 1) which has a bank account with the same bank account number as the new bank account just created 5. A banner will pop up at the top of the contact saying that this partner uses the same bank account as the partner you set on the bank account in step 2 Solution: Add a condition to the JOIN clause that checks “other.active = TRUE” to ensure that other res_partner_bank records to search for that have the same account number are active. Also add a condition to the WHERE clause that checks “this.active = TRUE” to ensure that the current res_partner_bank record doing the search is active itself. opw-4967083 Forward-Port-Of: odoo/odoo#231585
Community users can now install the Gelato integration from settings without being prompted to upgrade to Enterprise. This removes an incorrect barrier and makes the setup flow work as intended for eligible users.
Original PR description
Remove the 'Enterprise' widget from Gelato setting, which prevented community users from installing Gelato module from settings without upgrading to enterprise.
This update fixes a small issue when accepting Urban Piper orders in the Belgian POS certification module. It helps ensure orders from that channel are processed correctly, reducing the chance of disruption for point-of-sale operations.
Original PR description
Fix small issue in `pos_blackbox_be` module when accepting orders from Urban Piper.
This fixes an issue where POS session numbers could skip after a failed cash posting. Session names now advance only when the operation succeeds, keeping records easier to follow and audit.
Original PR description
Before this commit, if an issue occurred while posting the cash details, the session sequence would still increment even though the operation failed, leading to gaps in session names. With this commit, the sequence only increments when the operation succeeds, ensuring continuous session naming without gaps. related: https://github.com/odoo/enterprise/pull/98157 opw-5180712 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#233784 Forward-Port-Of: odoo/odoo#233183
This fix prevents Belgian POS session names from skipping numbers when posting cash details fails. The sequence is now only used after a successful operation, helping keep session records consistent for compliance and audit purposes.
Original PR description
Before this commit, if an issue occurred while posting the cash details, the session sequence would still increment even though the operation failed, leading to gaps in session names. With this commit, the sequence only increments when the operation succeeds, ensuring continuous session naming without gaps. related: https://github.com/odoo/odoo/pull/233183 opw-5180712 Forward-Port-Of: odoo/enterprise#98468 Forward-Port-Of: odoo/enterprise#98157