Odoo Changelog — 2026-02-28

Saturday, February 28, 2026

5 changes · master

Improvements(5)

Enhancements to existing features

[IMP] hr_contract_salary, l10n_be_hr_contract_salary: restrict BE-only fields

Enterprisemasterhr_contract_salaryl10n_be_hr_contract_salary

This update simplifies the employee salary configuration by removing irrelevant fields and restricting access to certain settings. Specifically, the 'Seniority at Hiring' input is now only available for Belgian companies, and demo data related to school and car plate information has been removed. This improves data accuracy and reduces complexity for Belgian users.

Original PR description

- Remove the School and Private Car Plate inputs from the employee salary configurator.
- Restrict the "Seniority at Hiring" input to Belgian companies only.
- Remove demo data and tour references related to study_school and private_car_plate.

task-5420271

#payroll#Belgium#configuration#data accuracy

[IMP] web: progress bar style

PR #55426

Enterprisemasterweb_enterpriseweb_studio

This update standardizes the appearance of progress bars across Odoo Enterprise, aligning with Bootstrap's design and adapting for dark mode. This simplifies the user interface and reduces the amount of code needed to maintain the progress bar style.

Original PR description

This commit implements a minor update to progress bars.

Customized progress bars have been replaced with Bootstrap standard styles with some adapation for the dark mode. This change streamlines the visual consistency but also reduces the CSS footprint.

Community PR: https://github.com/odoo/odoo/pull/151758

task-3605453

#ui#design#bootstrap

[IMP] voip(_ai): various refs/improvements

PR #108907

EnterprisemastervoipMEDIUM

This update enhances the reliability of call management by allowing calls to be ended before they start, using client-side timestamps for greater accuracy and responsiveness. This eliminates a previous dependency on server response times, improving system stability and reducing potential delays. It also streamlines code maintenance and improves readability.

Original PR description

There are 2 commits in that PR: # [REF] voip(_ai): align Session and Registerer conventions Harmonize Session and Registerer to ease maintenance and readability: - Rename _sipSession to…

There are 2 commits in that PR:

# [REF] voip(_ai): align Session and Registerer conventions
Harmonize Session and Registerer to ease maintenance and readability:

- Rename _sipSession to __sipJsSession in Session, matching the
  convention used in Registerer and UserAgent.
- Unify the stateChange listener pattern across both classes.
- Store isRegistered on the Registerer and trigger a bus notification
  on change, similarly to what is done in Session.

# [IMP] voip: allow end_call before start_call with explicit timestamps
Both start_call and end_call now accept an explicit `at` timestamp,
captured on the client at event time. New state transitions
(calling/missed → terminated) allow end_call to proceed independently
of start_call, with placeholder logic to reconcile start_date and
duration regardless of arrival order.

This removes the need to wait for start_call's response before
ending a call, improving system reliability in case the server
becomes unreachable. Using client-side timestamps also improves the
accuracy of start_date and duration, as they reflect the actual
event times rather than when the server processed the requests.

Preparatory work for task-4917399.

#voip#call management#reliability

[IMP] mail: improve notification settings thread action

PR #109077

EnterprisemasterdiscussMEDIUM

This update streamlines the user experience by changing how notification settings are accessed from the Discuss sidebar. Previously, settings opened in a dialog, now they open in a dropdown, creating a more consistent and user-friendly interface.

Original PR description

Before this PR, opening the notification settings from the thread action in the Discuss sidebar displayed them in a dialog, making the UI inconsistent with other thread actions.

After this PR, the notification settings open in a dropdown instead of a dialog, ensuring a more consistent and streamlined user experience.

community: https://github.com/odoo/odoo/pull/247352
task-5936685

Forward-Port-Of: odoo/enterprise#108523

#UI#Discuss#Notifications

[IMP] account_accountant: Replace account groups with account parent

PR #103845

EnterprisemasteraccountMEDIUM

This update simplifies account organization by replacing account groups with a parent account hierarchy. This change addresses previous limitations related to code ranges and reporting, offering a more flexible and user-friendly approach for financial reporting across different countries and business needs. It improves clarity and reduces complexity in how accounts are categorized.

Original PR description

Problems of account groups:
1. It's defined by code range. This means that it forces the use of codes and it creates the constraint that an account must be within a code range to be part of a group. This makes sense in countries like Belgium where there is a normalized plan, but this is a problem in countries where there is no normalized plan or in countries where the use of codes is optional (eg. USA).
2. It shows the code in front of the group in accounting reports (not always desirable).
3. It's difficult to discover.
4. It doesn't allow to use a group as an "intermediary account" in the hierarchy. (eg. using the account "Automobile" on a bill even though "Automobile" is a parent).
5. It doesn't display the CoA hierarchy.

task-5055586

#accounting#reporting#hierarchy

- Remove the School and Private Car Plate inputs from the employee salary configurator. - Restrict the "Seniority at Hiring" input to Belgian companies only. - Remove demo data and tour references related to study_school and private_car_plate. task-5420271

This commit implements a minor update to progress bars. Customized progress bars have been replaced with Bootstrap standard styles with some adapation for the dark mode. This change streamlines the visual consistency but also reduces the CSS footprint. Community PR: https://github.com/odoo/odoo/pull/151758 task-3605453

There are 2 commits in that PR: # [REF] voip(_ai): align Session and Registerer conventions Harmonize Session and Registerer to ease maintenance and readability: - Rename _sipSession to __sipJsSession in Session, matching the convention used in Registerer and UserAgent. - Unify the stateChange listener pattern across both classes. - Store isRegistered on the Registerer and trigger a bus notification on change, similarly to what is done in Session. # [IMP] voip: allow end_call before start_call with explicit timestamps Both start_call and end_call now accept an explicit `at` timestamp, captured on the client at event time. New state transitions (calling/missed → terminated) allow end_call to proceed independently of start_call, with placeholder logic to reconcile start_date and duration regardless of arrival order. This removes the need to wait for start_call's response before ending a call, improving system reliability in case the server becomes unreachable. Using client-side timestamps also improves the accuracy of start_date and duration, as they reflect the actual event times rather than when the server processed the requests. Preparatory work for task-4917399.

Before this PR, opening the notification settings from the thread action in the Discuss sidebar displayed them in a dialog, making the UI inconsistent with other thread actions. After this PR, the notification settings open in a dropdown instead of a dialog, ensuring a more consistent and streamlined user experience. community: https://github.com/odoo/odoo/pull/247352 task-5936685 Forward-Port-Of: odoo/enterprise#108523

Problems of account groups: 1. It's defined by code range. This means that it forces the use of codes and it creates the constraint that an account must be within a code range to be part of a group. This makes sense in countries like Belgium where there is a normalized plan, but this is a problem in countries where there is no normalized plan or in countries where the use of codes is optional (eg. USA). 2. It shows the code in front of the group in accounting reports (not always desirable). 3. It's difficult to discover. 4. It doesn't allow to use a group as an "intermediary account" in the hierarchy. (eg. using the account "Automobile" on a bill even though "Automobile" is a parent). 5. It doesn't display the CoA hierarchy. task-5055586