Odoo Changelog — 2025-07-11

Friday, July 11, 2025

4 changes

Refactoring(4)

Code cleanup and technical improvements

[REF] *: ControlPanel's buttons should be direct children

Enterprisemasteraccount_accountantaccount_bank_statement_importaccount_online_synchronizationappointmentcrm_enterprisedata_cleaninghr_payrollindustry_fsm_salel10n_be_reportsl10n_in_reportsl10n_ke_edi_oscu_posplanningsign

This update streamlines how action buttons are displayed across several Odoo screens by removing unnecessary layout wrappers. The change should make the interface structure cleaner and easier to maintain, with little to no visible change for end users.

Original PR description

This commit cleans up and simplifies the structure of the buttons
provided by the views/actions and displayed in the ControlPanel (or
modal's footer for the FormView). The point is to avoid unnecessary
wrapper around them, reducing the DOM and also the rules necessary to
handle the buttons' layout, gap...

task-4277543

#control-panel#buttons#interface#maintenance

[REF] *: Domain.optimize_full

PR #89935

Enterprisemasterindustry_fsm_saleproject_enterprise

This change refactors how the system handles domain logic used to filter and organize records. It should not change day-to-day behavior, but it helps keep project and field service sales features easier to maintain and improve over time.

Original PR description

Refactor of the API for Domain.

#maintenance#project#field-service

[REF] hr_holidays : remove dead code

PR #88931

Enterprisemasterhr_holidaysl10n_be_hr_payroll_account

This update cleans up unused code left behind after a user experience refactor in the time-off area. It helps keep the system easier to maintain without changing day-to-day functionality for users.

Original PR description

task-4893623

#cleanup#time-off#maintenance

[REF] mail, various: unstore 'record_name' on message

PR #86621

Enterprisemasterfrontdeskhelpdeskhr_appraisalhr_appraisal_surveyhr_contract_salarymail_mobilesigntest_mail_enterprisetest_whatsappwhatsappMEDIUM

Messages no longer keep a separate stored record name, reducing outdated or inconsistent labels and simplifying how message context is displayed. Related areas such as Helpdesk, Appraisals, Sign, WhatsApp, Frontdesk, and mobile messaging now rely on the current record name or explicitly provide one when needed.

Original PR description

Reasons to remove record_name
  * it is not synchronized, and synchronizing it would be very costly.
    This makes searching on record_name / grouping / ... useless;
  * some flows even set it to False to speedup sub records creation
    and avoid calling display_name on a lot of records e.g. mass
    mailing;
  * it is unnecessary to store it in most cases;
  * its main usage is in discuss / chatter where it is anyway based
    on actualy display_name;

In conclusion: get rid of stored 'record_name' field, simplify message
model by making it a computed field displaying the related record
display_name, and let flows displaying / managing messages handle
record names as they want to.

Task-4690371

#messages#notifications#record names#mail

This commit cleans up and simplifies the structure of the buttons provided by the views/actions and displayed in the ControlPanel (or modal's footer for the FormView). The point is to avoid unnecessary wrapper around them, reducing the DOM and also the rules necessary to handle the buttons' layout, gap... task-4277543

Reasons to remove record_name * it is not synchronized, and synchronizing it would be very costly. This makes searching on record_name / grouping / ... useless; * some flows even set it to False to speedup sub records creation and avoid calling display_name on a lot of records e.g. mass mailing; * it is unnecessary to store it in most cases; * its main usage is in discuss / chatter where it is anyway based on actualy display_name; In conclusion: get rid of stored 'record_name' field, simplify message model by making it a computed field displaying the related record display_name, and let flows displaying / managing messages handle record names as they want to. Task-4690371