Thursday, September 25, 2025
10 changes · 17.0
Enhancements to existing features
The tax search view now includes the tax amount field, making it easier for users to find taxes by their configured percentage or fixed amount. This reduces time spent locating the right tax record and improves day-to-day accounting usability.
Original PR description
This commit improves the usability of the tax search view by including the `amount` field. Users can filter taxes based on their configured percentage or amount directly from the search bar. task-5088050
Resolved issues and error corrections
This fix swaps two Mexican DIOT report columns so exempt imports and exempt amounts appear in the correct positions. The values were already calculated correctly, but the corrected ordering helps ensure exported reports match the expected official layout.
Original PR description
Description of the issue/feature this PR addresses: The description of the columns “exempt imports” and “exempt” is somewhat ambiguous, so when developing the diot, there was a small error in the order of the columns. The values are calculated correctly, but columns 49 and 50 were inadvertently swapped. Current behavior before PR: “exempt” is column 49 “exempt imports” is column 50 Desired behavior after PR is merged: “exempt” is column 50 “exempt imports” is column 49 Task-id: 5096808 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Documentation and clarification updates
This update adds new members to the Adhoc corporate contributor license agreement records. It keeps Odoo's legal contributor documentation current so contributions remain properly covered.
Original PR description
--- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#226715
Miscellaneous changes
This work touches the website module's dynamic snippet behavior, which controls how selected content blocks appear on website pages. Because the pull request is still marked as work in progress and lacks a detailed description, the expected business impact appears limited until more information is provided.
Original PR description
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
The Mexican DIOT report export now places the “exempt imports” and “exempt” values in the correct columns. This fixes a formatting issue in the downloaded TXT file so businesses can submit reports with the expected column layout, while the underlying calculated values remain unchanged.
Original PR description
The description of the columns “exempt imports” and “exempt” is somewhat ambiguous, so when developing the diot, there was a small error in the order of the columns. The values are calculated correctly, but columns 49 and 50 were inadvertently swapped. This Pr changes the order of the columns in the downloadable file (txt) and corrects the tests due to the change. Task-id: 5096808 I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an issue where users could see raw HTML text instead of a properly formatted help message when no bank transactions were found. This makes the bank journal experience clearer and more professional when fetching transactions or changing filters.
Original PR description
Before this commit: - The help message displayed raw HTML tags when no transactions were returned after clicking 'Fetch Transactions' in the Bank journal. - Also, removing a filter (without reloading) and applying another filter that resulted in no matches, the same issue occurred. After this commit: - The help message is now consistently rendered with proper markup task-4942234
Point of Sale self-order sessions now remove their temporary numbering data when a session is closed. This helps keep the database tidier over time and avoids buildup from repeated sessions, with no expected change to the checkout experience.
Original PR description
to avoid having too many postgres sequences, this make sure the sequence used by the pos session is cleaned up after being closed. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix makes a purchase stock test use the intended type of product regardless of other installed localization modules. It helps prevent false test failures and keeps quality checks reliable without changing day-to-day business workflows.
Original PR description
The test `test_receive_negative_quantity` is failing when run with the `l10n_ke` module installed. The failure occurs during the validation of the picking created from a negative-quantity purchase…
The test `test_receive_negative_quantity` is failing when run with the `l10n_ke` module installed. The failure occurs during the validation of the picking created from a negative-quantity purchase order. The test assumes the product is of type `consu`, which bypasses stock reservation. However, the following [XML default](https://github.com/odoo/enterprise/blob/17.0/l10n_ke_edi_oscu_stock/data/ir_default.xml#L5) in l10n_ke forces the product type to `product` (stockable), triggering reservation logic. Since the ordered quantity is negative, no reservation occurs, and the `_sanity_check()` fails with: `You cannot validate a transfer if no quantities are reserved.` We fix this by explicitly setting a product with the type `consu` in the test. This ensures that reservation is skipped regardless of which modules are installed or what defaults they apply. runbot:[108147](https://runbot.odoo.com/odoo/error/108147) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Scanning a product or lot in the Barcode app now opens the same kanban-style view used elsewhere in barcode workflows. This makes the experience more consistent and helps warehouse users avoid switching from an unexpected list view.
Original PR description
This commit is to show the kanban view as a default when scanning a product or a lot in barcode. Before PR: All views in barcode are in kanban view except when scanning a product or a lot, it appears in list view. After PR: Now barcode also shows kanban view when scanning a product or a lot.
This fixes an issue where borders added to images in email designs disappeared after sending. Email recipients will now see image borders as intended, improving consistency between the editor preview and delivered emails.
Original PR description
Problem: When adding a border to an image and sending an email, the border is not visible in the received email. Solution: Ensure a `border-style` is set if missing, otherwise keep the existing one. Steps to reproduce: - Open email marketing. - Add an image snippet. - Add a border to the image. - Send the email. - The received image has no border. opw-5004824 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr