Monday, May 19, 2025
12 changes · 17.0
Enhancements to existing features
This commit adds translations for Luxembourg Annual VAT Declaration in the official languages of Luxembourg. The translation is added for languages Luxembourgish, German, and French. task-4717339
Original PR description
This commit adds translations for Luxembourg Annual VAT Declaration in the official languages of Luxembourg. The translation is added for languages Luxembourgish, German, and French. task-4717339
Resolved issues and error corrections
This change stabilizes an automated test for mail presence tracking by ignoring an unrelated background update that could run in a different order. It reduces false test failures in the build pipeline without changing user-facing mail behavior.
Original PR description
The `subscribe to known partner presences` test ensures that a bus subscription is sent when discovering a new partner whose presence needs tracking. However, the test triggers a channel join, which itself causes a bus subscription. Since both `add_channel` and `force_update_channels` are debounced, the outcome depends on which one executes first. As a result, `force_update_channels` may or may not include the newly added channel, making the test non-deterministic. In practice, this doesn't matter: if `force_update_channels` omits the new channel, `add_channel` will later update the subscription as needed. This commit resolves the issue by ignoring `force_update_channels` in the test, since it's irrelevant in this context. fixes runbot-161223,182043,182044
Documentation and clarification updates
This pull request adds Jonathan Stein's contributor license agreement documentation. It supports the project's legal compliance process and does not change any product functionality.
Original PR description
Adding CLA
Miscellaneous changes
Abandoned cart emails would send twice because the email values for the abandoned cart template would include the partner on the record already, but we were also including the partner email in the email values. Adjusted the email values to be empty when there is already a recipient found on the template. opw-4684534 Forward-Port-Of: odoo/odoo#206158
Original PR description
Abandoned cart emails would send twice because the email values for the abandoned cart template would include the partner on the record already, but we were also including the partner email in the email values. Adjusted the email values to be empty when there is already a recipient found on the template. opw-4684534 Forward-Port-Of: odoo/odoo#206158
The Preview button is no longer shown on draft invoices, preventing users from opening a feature that is not available before posting. This avoids a misleading option and the error that occurred when users tried to preview an unposted invoice.
Original PR description
The "Preview" button was visible even when the invoice was still in draft state, which could mislead users as the feature isn't meant for unposted entries. This fix updates the button visibility condition to exclude both cancelled and draft invoices. Steps to reproduce: Go to Invoices New Invoice You can see the preview button and if you click on it an error occurs OPW-4749877 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update prevents online bank synchronization from failing when older transaction details are stored as text instead of structured data. It helps ensure bank statement processing remains reliable for databases using versions before 18.2.
Original PR description
In this commit: https://github.com/odoo/enterprise/pull/84728/commits/d3b3de47ca3f174e97eb598187b32e31077a2ddb since the transaction details field was in fact a string in version lower than 18.2 the get would traceback no task id
Backport of 56d2d8b303e9c7909d29aa532cb0d717a7b57ed2 `payment` does not depend on `account`, it thus can't unconditionally use `account` groups. Skip tests if `account` is not installed (matches `account_custom` behaviour). `account_custom` does not depend on `product`, so can't use `product.product` unconditionally. runbot-163119 Forward-Port-Of: odoo/odoo#210381
Original PR description
Backport of 56d2d8b303e9c7909d29aa532cb0d717a7b57ed2 `payment` does not depend on `account`, it thus can't unconditionally use `account` groups. Skip tests if `account` is not installed (matches `account_custom` behaviour). `account_custom` does not depend on `product`, so can't use `product.product` unconditionally. runbot-163119 Forward-Port-Of: odoo/odoo#210381
Steps to Reproduce: --- 1. Create a tax with the following settings: > - Rate: 12% > - Price Included: True > - Affect Base of Subsequent Taxes: False. 2. Create another tax with the following settings: > - Type: Python Code > - Code: result = 22.503 > - Price Included: True > - Affect Base of Subsequent Taxes: False. > - Ensure the sequence of this tax is greater than the 12% tax (this tax is after the 12% tax in order). 3. Create a product with a sales price of 516.00 and
Original PR description
Steps to Reproduce: --- 1. Create a tax with the following settings: > - Rate: 12% > - Price Included: True > - Affect Base of Subsequent Taxes: False. 2. Create another tax with the following…
Steps to Reproduce: --- 1. Create a tax with the following settings: > - Rate: 12% > - Price Included: True > - Affect Base of Subsequent Taxes: False. 2. Create another tax with the following settings: > - Type: Python Code > - Code: result = 22.503 > - Price Included: True > - Affect Base of Subsequent Taxes: False. > - Ensure the sequence of this tax is greater than the 12% tax (this tax is after the 12% tax in order). 3. Create a product with a sales price of 516.00 and assign both taxes to it. 4. Create a new invoice and add the product to the invoice. The total will show an extra 0.01 due to rounding. Cause: --- When applying price-included taxes with multiple taxes, the rounding difference is carried to the last tax to ensure the total matches the product's tax-included price. However, cached values for Python code taxes were used even for the last tax, preventing the rounding correction from being applied. Fix: --- An additional condition was added to ensure cached values are only used when there is no price total checkpoint, allowing the rounding correction to be applied to the last tax. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#207665
Steps to reproduce: 1) Create another payment method of type cash 2) Add to POS 3) Open a pos session 4) Set a customer 5) Add a product, check out 6) Select your new payment method 7) Make sure 'Invoice' is marked to generate an invoice Issue: Validate -> error Cause: We have multiple cash payment method We should only have one and the one selectd manually opw-4503848 Forward-Port-Of: odoo/odoo#204171
Original PR description
Steps to reproduce: 1) Create another payment method of type cash 2) Add to POS 3) Open a pos session 4) Set a customer 5) Add a product, check out 6) Select your new payment method 7) Make sure 'Invoice' is marked to generate an invoice Issue: Validate -> error Cause: We have multiple cash payment method We should only have one and the one selectd manually opw-4503848 Forward-Port-Of: odoo/odoo#204171
Before this commit, resizing columns in list views when being in right-to-left didn't work as expected: when resizing a column, the column was resized in the opposite direction. This commit makes it work. opw~4782197 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 Forward-Port-Of: odoo/odoo#210290
Original PR description
Before this commit, resizing columns in list views when being in right-to-left didn't work as expected: when resizing a column, the column was resized in the opposite direction. This commit makes it work. opw~4782197 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 Forward-Port-Of: odoo/odoo#210290
Steps to print the check: 1. Ensure l10n_us_check_printing is installed 2. Set the check layout to Print Check (Middle) - US 3. Create a PO and a bill from it. 4. Create a payment for the bill using checks as your payment method 5. Click Print Check on the payment Current behavior before PR: The checks would print the vendor's name in the stubs, and the date alignment in the (middle) format was overlapping with the check number. Description of the issue/feature this PR addresses: Th
Original PR description
Steps to print the check: 1. Ensure l10n_us_check_printing is installed 2. Set the check layout to Print Check (Middle) - US 3. Create a PO and a bill from it. 4. Create a payment for the bill using…
Steps to print the check: 1. Ensure l10n_us_check_printing is installed 2. Set the check layout to Print Check (Middle) - US 3. Create a PO and a bill from it. 4. Create a payment for the bill using checks as your payment method 5. Click Print Check on the payment Current behavior before PR: The checks would print the vendor's name in the stubs, and the date alignment in the (middle) format was overlapping with the check number. Description of the issue/feature this PR addresses: The checks are aligned with the expected format and conditionally render the correct fields in the document's intended areas. Desired behavior after PR is merged: The printed check will now match the format and alignment of the templates used here: https://checkdepot.net/collections/odoo-checks/products/odoo-checks-top- format. Additionally, the check will now avoid printing the issuing company name on the stubs when the manual numbering setting on the bank journal is switched off. This assumes that the checks are preprinted with the company name and check number. opw-4557006 opw-4738359 Enterprise PR: https://github.com/odoo/enterprise/pull/84644 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#208357
Steps to print the check: 1. Ensure l10n_us_check_printing is installed 2. Set the check layout to Print Check (Middle) - US in the settings 3. Create a PO and a bill from it. 4. Create a payment for the bill using checks as your payment method 5. Click Print Check on the payment The printed check will now match the format and alignment of the templates used [here](https://checkdepot.net/collections/odoo-checks?_pos=1&_psq=odoo&_ss=e&_v=1.0). Additionally, the check will now avoid printi
Original PR description
Steps to print the check: 1. Ensure l10n_us_check_printing is installed 2. Set the check layout to Print Check (Middle) - US in the settings 3. Create a PO and a bill from it. 4. Create a payment for…
Steps to print the check: 1. Ensure l10n_us_check_printing is installed 2. Set the check layout to Print Check (Middle) - US in the settings 3. Create a PO and a bill from it. 4. Create a payment for the bill using checks as your payment method 5. Click Print Check on the payment The printed check will now match the format and alignment of the templates used [here](https://checkdepot.net/collections/odoo-checks?_pos=1&_psq=odoo&_ss=e&_v=1.0). Additionally, the check will now avoid printing the issuing company name on the stubs when the manual numbering setting on the bank journal is switched off. This assumes that the checks are preprinted with the company name and check number. Before the fix, the checks printed the vendor's name in the stubs, and the date alignment in the (middle) format overlapped with the check number. After the fix, the checks are aligned with the expected format and conditionally render the correct fields in the document's intended areas. opw-4557006 opw-4738359 odoo PR: https://github.com/odoo/odoo/pull/208357 Forward-Port-Of: odoo/enterprise#84644