This update renames an internal mail notification preview component used in enterprise messaging. It helps keep the codebase clearer and more consistent without changing how users interact with notifications.

*: mail_enterprise

Task-3048021

This update renames an internal notification display component in the enterprise mail area to improve consistency and maintainability. It does not introduce a visible workflow change for users, but helps keep the messaging interface code clearer for future improvements.

*: mail_enterprise

Task-3047829

The mail enterprise interface has been updated to use a clearer internal name for the notification list component. This is a maintenance improvement that helps keep the codebase consistent without changing day-to-day user behavior.

*: mail_enterprise

Task-3047871

The Documents app was updated to align with a renamed follower menu component used across Odoo. This is an internal cleanup that helps keep the codebase consistent and easier to maintain, with no expected change to daily user workflows.

*: documents

Task-3047236

The Mail Enterprise message list component has been renamed to align with the broader mail application structure. This is an internal cleanup that helps keep the codebase consistent and easier to maintain, with no expected change to day-to-day user workflows.

*: mail_enterprise

Task-3047718

The update renames an internal mail message component and adjusts related automated tests across several Odoo apps. This helps keep the product codebase clearer and more consistent, with no expected direct change to day-to-day user workflows.

*: documents, mail_enterprise,
   test_l10n_be_hr_payroll_account, website_helpdesk_knowledge

Task-3047352

This update renames the Discuss component within the enterprise mail area to keep the product wording consistent. It helps users and testers see clearer, aligned naming across related mail features without changing core functionality.

*: mail_enterprise

Task-3046685

The messaging text input component was renamed across related enterprise areas to keep the codebase consistent. This is an internal maintenance improvement that helps future development and testing without changing the user experience.

*: documents, mail_enterprise, website_helpdesk_livechat

Task-3046648

The internal name of the messaging composer component was updated consistently across Documents, Knowledge, Mail Enterprise, and Website Helpdesk Live Chat. This improves maintainability and consistency for future updates without introducing a significant change to day-to-day user workflows.

*: documents, knowledge, mail_enterprise, website_helpdesk_livechat

Task-3046555

This update renames an internal attachment display component to make its purpose clearer for future development. It does not change customer-facing behavior, but it helps keep the mail and knowledge-related code easier to maintain.

Task-3046129

This update renames an internal mail activity component to better reflect how it is used in the interface. The change helps keep the codebase clearer and easier to maintain, with no expected impact on day-to-day users.

Task-3046113

This update renames an internal chat window header component in Odoo’s Enterprise mail area. It keeps the codebase clearer and easier to maintain, with no expected change to how users interact with chat windows.

*: mail_enterprise

Task-3046330

This PR includes two commits which fix formatting bugs in the timesheets-entry form view and the planning no-email wizard form view. Both of the bugs were introduced by the 16.0 merge Task-3046054 Forward-Port-Of: odoo/enterprise#33301

This PR includes two commits which fix formatting bugs 
in the timesheets-entry form view and the planning
no-email wizard form view. 

Both of the bugs were introduced by the 16.0 merge

Task-3046054

Forward-Port-Of: odoo/enterprise#33301

Purpose ======= Onchange methods are executed in "edit-mode", so you need to save to get the definitive values saved on the DB, but if you do a write on it, that changes are immediately saved to the DB, so if you discard the changes on UI, you will have inconsistent data. That's why you have to do update instead, that only modifies the temporary dataset. Courtesy of https://github.com/OCA/pylint-odoo/issues/356 TaskID: 3046426 Forward-Port-Of: odoo/enterprise#33366

Purpose
=======

Onchange methods are executed in "edit-mode", so you need to save to get the definitive values saved on the DB, but if you do a write on it, that changes are immediately saved to the DB, so if you discard the changes on UI, you will have inconsistent data. That's why you have to do update instead, that only modifies the temporary dataset.

Courtesy of https://github.com/OCA/pylint-odoo/issues/356

TaskID: 3046426

Forward-Port-Of: odoo/enterprise#33366

Before this commit, we had the following issues: 1. When chatting with an achieved user(like a public user), the user name was not displayed in /helpdesk command message. 2. When chatting with self(current), the user's name is not displayed in the same command. So in this commit, Get the archived channel partners too and if the partner is chatting with self then display the current user's partner name in the helpdesk chat message. task-2969228 Forward-Port-Of: odoo/enterprise#33303

Before this commit, we had the following issues:
  1. When chatting with an achieved user(like a public user), the user name was not displayed in /helpdesk command message.
  2. When chatting with self(current), the user's name is not displayed in the same command.

So in this commit, Get the archived channel partners too and if the partner is chatting with self then display the current user's partner name in the helpdesk chat message.

task-2969228

Forward-Port-Of: odoo/enterprise#33303
Forward-Port-Of: odoo/enterprise#31142