Sunday, November 24, 2024
4 changes
3 changes
Features or functions removed from Odoo
The spreadsheet pivot side panel no longer uses a separate Odoo-specific highlighting behavior. Highlighting is now handled consistently by the shared spreadsheet engine for all pivot types, reducing duplicate logic and improving consistency.
Original PR description
This removes the code creating highlights for odoo pivot in the side panel. It is now handled in o-spreadsheet directly for all pivot types. Task: 4341467
The spreadsheet pivot side panel no longer uses a separate Odoo-specific highlight behavior. Highlighting is now handled centrally in the spreadsheet engine for all pivot types, making behavior more consistent and reducing duplicate maintenance.
Original PR description
This removes the code creating highlights for odoo pivot in the side panel. It is now handled in o-spreadsheet directly for all pivot types. Task: [4341467](https://www.odoo.com/web#id=4341467&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)
Miscellaneous changes
When a whatsapp conversation is inactive after 1 day, they are automatically unpinned as long as user has seen all the messages. However, if the user never reads them, these whatsapp conversations keep being added to the pinned list of conversations, which adds more and more loads on Discuss fetched data over time. There is a practical limit of around 2000 pinned conversations, after which Discuss is very slow and hardly usable. This is a known limitation with the current implementation.
Original PR description
When a whatsapp conversation is inactive after 1 day, they are automatically unpinned as long as user has seen all the messages. However, if the user never reads them, these whatsapp conversations…
When a whatsapp conversation is inactive after 1 day, they are automatically unpinned as long as user has seen all the messages. However, if the user never reads them, these whatsapp conversations keep being added to the pinned list of conversations, which adds more and more loads on Discuss fetched data over time. There is a practical limit of around 2000 pinned conversations, after which Discuss is very slow and hardly usable. This is a known limitation with the current implementation. Whatsapp conversations usually involved many operators for a given conversation, even though usually a single operator is actively communicating with the whatsapp customer. This means that all the inactive operators are keeping many unread whatsapp conversations, thus lots of whatsapp conversations stay unpinned. This commit fixes the issue by forcing unpinning inactive whatsapp conversations after 2 weeks, regardless of whether current user has read the conversation or not. Most of the time whatsapp conversations are short-lived conversations, therefore after 2 weeks this is almost guarantee that there's no point keeping this conversation pinned. opw-4331007 Forward-Port-Of: odoo/enterprise#74131 Forward-Port-Of: odoo/enterprise#73923
1 change
Miscellaneous changes
Current behavior before PR: When a user posted a message in a group chat, the web notification displayed `#False` as the title. This occurred because `record_name` was used as the title but it was empty for channels with `channel_type = 'group'`, as the displayName name is calculated on the UI side when displaying chat in Discuss. Before / After <div style="display: flex;"> <img src="https://github.com/user-attachments/assets/7ad2de52-8cef-41a7-8d63-b19d718725ff" width="48%" style="margi
Original PR description
Current behavior before PR: When a user posted a message in a group chat, the web notification displayed `#False` as the title. This occurred because `record_name` was used as the title but it was empty for channels with `channel_type = 'group'`, as the displayName name is calculated on the UI side when displaying chat in Discuss. Before / After <div style="display: flex;"> <img src="https://github.com/user-attachments/assets/7ad2de52-8cef-41a7-8d63-b19d718725ff" width="48%" style="margin-right: 4%;" /> <img src="https://github.com/user-attachments/assets/452fac6e-3a79-4e53-a09c-4fad57b44856" width="48%" /> </div> Desired behavior after PR is merged: The title of the web notification now correctly displays the group chat name, ensuring recipients see accurate and complete group titles in notifications. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#187657 Forward-Port-Of: odoo/odoo#186756