Sunday, July 6, 2025
6 changes
5 changes
Enhancements to existing features
The live chat information panel now shows more customer context, including open leads, open support tickets, chatbot answers, and conversation outcomes. This helps teams understand each chat faster and follow up 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 https://github.com/odoo/enterprise/pull/89573 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Live chat conversations that have ended now show a checkered flag indicator in the Discuss sidebar and on chat bubbles. This helps support teams quickly identify closed or inactive chats without opening each conversation.
Original PR description
Before this commit, seeing whether a livechat has ended, e.g. due to visitor leaving, required opening the conversation and seeing the "livechat has ended" where composer is shown. This commit improves visibility of livechat that have ended by showing a checkered flag icon on avatar of livechat conversation that have ended. This icon is also shown on chat bubbles. <img width="293" alt="Screenshot 2025-07-05 at 21 55 16" src="https://github.com/user-attachments/assets/5918fc19-9397-40c7-84ff-be34f6f8552d" />
Website and HTML builder options can now wait for background state updates before refreshing related controls. This helps keep image, form, card, carousel, and animation settings consistent when edits depend on asynchronous updates.
Original PR description
Whenever there is a need to update the state of a builder option asynchronously, we need all the options to await for the state of all other options to be updated. This commit makes allow any options that need to update the state of the builder options asynchronously to do so by using the `useDomState` hook. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Mobile users can now open message actions with a long press, copy message text, and use reaction menus that appear more consistently at the bottom of the screen. The update makes Discuss easier to use on phones and avoids confusing background overlay changes when navigating message options.
Original PR description
This PR improves several aspects of discuss on mobile devices: - Long press to open message actions - Fix background color issue when opening sub-menu from message actions - Improve reaction menu position - Add a copy action for messages | - | Before | After | | -------------| ------------- | ------------- | | Background ||  | | Reaction menu |  |  | enterprise: https://github.com/odoo/enterprise/pull/89402
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 each visitor faster and respond with more relevant next steps.
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
1 change
Enhancements to existing features
This update helps Turkish e-invoices meet GIB requirements by using the customer reference field as the registered tax office name in Nilvera documents. Users will now see warnings or validation errors if an e-invoice customer is missing this required information, reducing the risk of non-compliant invoices.
Original PR description
### Description of the issue/feature this PR addresses This PR adds a validation to ensure that E-Invoice partners in Turkey have the `reference` field filled with their registered tax office name,…
### Description of the issue/feature this PR addresses This PR adds a validation to ensure that E-Invoice partners in Turkey have the `reference` field filled with their registered tax office name, as required by GİB regulations. ### Current behavior before PR Partners marked as E-Invoice customers can be used in invoicing without a value in the `reference` field, which may lead to non-compliant UBL documents. ### Desired behavior after PR is merged Once the reference field is filled, it is sent via the UBL, as it is passed to tax_scheme_vals. The account move send wizard issues a critical warning for partners that should have the tax office name in the reference field. If this warning is ignored and the customer on the invoice has a TR e-invoicing status of Nilvera, a validation error is raised, prompting the user to complete the required reference field on the customer. Task-4886128 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#215772