Monday, November 10, 2025
3 changes · 19.0
Enhancements to existing features
The bank statement validation check was optimized to run much faster by using a more efficient database query. This reduces processing time and database load, which can help the accounting app respond more quickly when checking many statements.
Original PR description
Description ----------- Avoid self-join of `account_bank_statement` that is done with a `Nested Loop` due to the `LATERAL`. Even if correlated, it requires two separate accesses to its index. Replaces it with a window function + `LAG` partitioned by the `journal_id`. This leads to a simpler plan (lower cost) and working in-memory instead of accessing disk pages (lower IO contention). Benchmark --------- On a database with 46k `account_bank_statement`, calling `_get_invalid_statement_ids` for all statements took: | [Before](https://explain.dalibo.com/plan/7605a4ddc42afbcf) | [After](https://explain.dalibo.com/plan/88d6ac1gee37aha3) | Speed-up | |--------|-------|----------| | 146ms | 72ms | 2x | --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#232980
When a website uses the cookie bar, new Google Fonts will now default to not loading directly from Google. This helps websites stay more aligned with GDPR expectations, and the updated help text makes the privacy impact clearer for users setting up fonts.
Original PR description
__Current behavior before commit:__ When the cookies bar is installed, Google fonts are still loaded from Google servers by default, which may violate GDPR requirements. See the PR adding the "Serve from Google"[1] option for more details. __Description of the change:__ If the cookies bar is enabled, it likely means that the website needs to be GDPR compliant. In this case the "Serve from Google" option is disabled by default when adding a new Google Font, preventing it from being served from Google servers. The tooltip and setting help text are also updated to clarify GDPR implications. [1]: https://github.com/odoo/odoo/pull/101129 task-5111612
Discuss now includes a dedicated live chat category for conversations marked as "Looking for Help." Agents also see a star indicator on chats that match their expertise, helping them spot and respond to the most relevant conversations faster.
Original PR description
Add a live chat category in the Discuss app that allows live chat agents to easily identify conversations marked as "Looking for Help." A star icon is added next to conversations that match the agent's expertise, making it easier to assist with conversations related to their area of expertise. part of task-5190237.