Monday, January 27, 2025
13 changes
2 changes
Resolved issues and error corrections
A minor issue in the Knowledge app's automated article command tour was corrected so the test can run successfully again. This helps maintain product quality by ensuring future changes to Knowledge article commands are checked reliably.
Original PR description
Following [this commit], in master, there was another change preventing the disabled test to run without error. This commit fixes the issue in order to be able to re-enable the test. [this commit]: https://github.com/odoo/enterprise/commit/02bf70e1ad8c7d88ce20f74ab4df5a00d59d52e9 runbot-task-111948
WhatsApp now uses the shared phone validation logic when looking up partners by phone number. This reduces duplicate handling and helps match contacts more consistently across the system.
11 changes
Resolved issues and error corrections
This fix stops an extra dialog from appearing in Point of Sale when the same register session is already being closed. It helps cashiers avoid confusion during the closing process and keeps the workflow smoother.
Original PR description
check commit message for description.
This fixes the status display for draft accounting entries so they once again appear with the expected blue badge. The change helps users quickly distinguish draft moves in accounting lists after a recent view update accidentally removed that visual cue.
Original PR description
In the account move view, since this commit: https://github.com/odoo/odoo/commit/9b47dd1158b2819c74431f30ff137cbb13ce0d4f We made a new column that is status_in_payment but with that we removed the decoration for draft moves task-4497735 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixes an issue where tables added to chatter messages could lose visible cell borders after being logged or sent. This helps users share formatted information more clearly and reliably in discussions.
Original PR description
**Problem**: When adding a table in the chatter and logging/sending, the table is not displayed properly. This issue is same as: https://github.com/odoo/odoo/commit/99c5a73b2ffc9bef6128059c51574c70cdfc6767. Grouped styles like `border`, `padding`, and `border-radius` do not propagate their values to substyles when variables are used in the value. **Solution**: Apply same fix in `convert_inline` of `mail` **Steps to Reproduce**: 1. Open the full composer. 2. Add a table. 3. Log a note. 4. Observe that `td` borders are not visible. opw-4483477 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users are now shown a clear warning when they try to use Print & Send on an invoice that has not yet been confirmed. This prevents a confusing system error caused by draft invoices not having a final invoice number for the PDF filename.
Original PR description
Currently, an error occurs when attempting to print and send an invoice that is in a draft state. Step to produce: - Install the `account` module. - Go to Invoicing / Customers / Invoices, Create one invoice without a customer and invoice line, and come to the list view of Invoices. - Select this invoice and click on 'Print & Send'. `AttributeError: 'bool' object has no attribute 'replace'` The issue occurs because the system attempts to replace the name at [1] to generate a PDF file name. But the invoice's name is not available. Link [1]: https://github.com/odoo/odoo/blob/41de88b930e569daea7624ee3655cef218f9136f/addons/account/models/account_move.py#L5739 To resolve this issue, Raise a user error if the user attempts to select the 'Print & Send' action on an invoice that is not in the confirmed state. Sentry-6185757435 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where users could not edit the description of a newly added service line on a confirmed sales order. The change keeps order line descriptions editable when appropriate, reducing friction when updating confirmed orders.
Original PR description
Steps: - Install sale_project - Create a service type product - Create a SO and confirm it - In the confirmed order add a SOL with the new product Issue: - cannot edit the description of the new SOL Cause: - readonly for the SOL is set based on product_updatable and product_updatable is set false when product type service even for new order line Fix - Updated the readonly condition to account for new lines opw - 4473488 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Sales order combo items now allow users to update the delivered quantity, not just the description and taxes. This fixes an editing limitation so delivered amounts can be corrected directly when needed.
Original PR description
Previously, only the description and taxes could be edited on combo item SOLs. However, the delivered quantity should also be editable. opw-4454205
The Sign app now sends users back to the project they came from after completing a signature request. This avoids opening an unnecessary new wizard and makes the workflow smoother for project users.
Original PR description
version: - 18.0 Steps to reproduce: - Install the Project and Sign modules. - Open a project. - Click on the "Signature Request" action. - Select a document and click "Sign Now." - Complete the signing process. - Click the "Back to Project" button. Issue: - Clicking "Back to Project" opens a new wizard instead of returning to the project view. Cause: - The project view is set to always open in a new target. Solution: - Update the target to "current" to ensure the button redirects correctly to the project view. task:4431882
Changing the date in the duplicate transaction finder no longer causes an error when results appear after an empty state. This makes the bank synchronization workflow more reliable for users reviewing potential duplicate transactions.
Original PR description
Fix traceback when changing the date in the find duplicate tool When the user changes the date in the find duplicate tool, a traceback occurs when transitioning from no rows displayed to rows being displayed. This issue is caused by the `getRowClass` function referencing the outdated `firstIdsInGroup` field, which is never updated. If there were no values initially, the function attempts to call `includes` on a `false` value, resulting in the error. This commit resolves the issue by removing the obsolete `firstIdsInGroup` field and adding a condition to ensure that the value being checked is an array, preventing any traceback. no task id
Financial report rows and columns will now keep the intended order automatically during database upgrades. This prevents reports from appearing in an unexpected sequence if the underlying report definitions change, reducing manual maintenance and upgrade risk.
Original PR description
Having no manual sequence on report lines/columns might be problematic in case of DB upgrade, if the line order changed in the xml files, as the report won't adapt and update the sequence field. Setting auto_sequence will ensure that this won't ever be a problem anymore (and avoid the tedious task of manually setting the sequence on each line/column)
Tax closing messages now show a clickable link to the related main closing entry instead of displaying raw HTML text. This makes it easier for accounting users to navigate between dependent tax closing entries and their parent entry.
Original PR description
When you had tax closing entries that depended on a main closing entry, the posting of that main entry would log a message on each depending entry containing a link to the main closing entry. In [this commit] the way that message is constructed was changed, making it safer but also causing the link HTML to be escaped. It would just show raw HTML in the logged message instead of a link. This commit constructs the message in a correct and safe way so the link works again in the logged message. [this commit]: https://github.com/odoo/enterprise/commit/09f5b35493bee7b63e96e8b28ad741aeb5ee80e5
Reconciled batch payments no longer appear as available options during bank reconciliation. This prevents users from accidentally seeing or selecting payments that have already been matched, keeping the reconciliation workflow clearer and more accurate.
Original PR description
### Steps to reproduce: - In Accounting, create a new Customer invoice - Create a payment for this invoice - In Customer > Batch Payments create a new batch payment - Select the payment you created - In the Dashboard click on the three dots of the "Bank" block and click on transactions - Create a new transaction with the same amount as the invoice - Click "Match" on the right - In the "Batch Payments" tab select the Batch payment previously created - Validate - Back in the Dashboard, click on the reconcile button of the Bank block - In the "Batch Payments" tab the batch payment is still here even if it is reconciled ### Cause: There are no domain to filter the batch payments. ### Solution: Add a domain to check the state of the batch payments, do not display if it is "reconciled". opw-4461341