Odoo Changelog — 2025-05-19

Monday, May 19, 2025

3 changes · 17.0

Bug Fixes(3)

Resolved issues and error corrections

[FIX] mail: make partner presence test deterministic

Core17.0mail

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

#testing#reliability#presence

[FIX] account: hide Preview button for draft invoices

PR #208386

Core17.0account

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

#invoices#preview#draft

[FIX] account_online_synchronization: json loads

PR #85848

Enterprise17.0account_online_synchronization

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

#bank synchronization#transactions#stability

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

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

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