Daily updates from Odoo
Monday, July 7, 2025
4 changes · master
Enhancements to existing features
The live chat information panel now shows more customer context, including open leads, open helpdesk tickets, chatbot answers, and conversation outcomes. This helps support and sales teams understand a visitor's situation faster and respond more effectively without switching screens.
Original PR description
Adding following features to info panel: - Display open leads in info panel - Display open tickets in info panel - Display chatbot answers in info panel - Display outcome in info panel follow up of task-4771890 Forward-Port-Of: odoo/enterprise#89573
Product cards in the online shop have been visually refreshed to provide a cleaner, more consistent shopping experience. This helps customers browse products more easily and supports a more polished storefront presentation.
Original PR description
Requires: - https://github.com/odoo/odoo/pull/214744
Helpdesk ticket stages now use consistent colors across views, making it easier for teams and customers to recognize a ticket's status at a glance. This improves visual clarity in Helpdesk and related project views without changing the underlying workflow.
Original PR description
This commit's purpose is to add a color consistency within helpdek stage. This will help to tell with one glance in which stage the ticket is.
Aged Receivable and related partner aging reports now avoid an unnecessary database lookup when calculating invoice dates. This can significantly reduce report loading time on very large accounting databases, improving day-to-day finance reporting performance without changing report results.
Original PR description
The Aged Partner reports query in `_aged_partner_report_custom_engine_common` is joining on the `account_move` table solely to get the `invoice_date` column. As this `invoice_date` is aggregated in `ARRAY_AGG(DISTINCT invoice_date)` and there's already a denormalized field `invoice_date` on `account_move_line` that is a related stored field, we can drop the join and use this field instead. This saves us the need to scan the account.move table when running the reports query. In a database with 37M amls, 10M account.move (and a really bad correlation for account_move_line.move_id), this saves us around 10 minutes for the Aged Receivable report's query. Forward-Port-Of: odoo/enterprise#89325