Odoo Changelog — 2025-01-24

Friday, January 24, 2025

6 changes · saas-18.1

Bug Fixes(6)

Resolved issues and error corrections

[FIX] mail: no flicker on call video stream inset

PR #194013

Coresaas-18.1mail

Discuss calls no longer show flickering in the small video preview when a user is sharing their screen and has the camera enabled. This creates a steadier, less distracting call experience for users.

Original PR description

Before this commit, during a discuss call while sharing screen and enabling camera, the inset card (= small video stream preview in bottom right of call view of the participant, either camera or screen-sharing depending on other stream being main active) was flickering.

This happens because each rendering of the call view re-renders the inset, which leads to the perceived flickers from stream being re-rendered.

The main cause of re-render comes from `setInset()` that is invoked whenever the `visibleMainCards` getter is called with inset, which is triggered on renderings like mouse-hovering on call view to display the call actions. Even when the inset card is unchanged, `setInset()` produces another object, which forces OWL to re-render the inset component.

This commit fixes the issue by having `setInset` reusing the inset data object if the inset to render refers to the same inset session.

Task-4484908

#discuss#video calls#screen sharing

[FIX] mail: multiple action_unfollow on livechat leave

PR #194316

Coresaas-18.1im_livechatmail

Leaving a livechat conversation from Discuss now avoids sending the same unfollow action twice. This reduces unnecessary background processing and helps keep livechat membership changes cleaner and more reliable for users.

Original PR description

Before this PR, leaving a livechat channel from the Discuss app would trigger multiple `action_unfollow` actions:
- One initiated by the Discuss app.
- Another triggered by the `channel/leave` notification.

This PR resolves the issue by ensuring that the `channel/leave` notification does not redundantly trigger an `action_unfollow`.

Task-4488437

Additionally, this commit addresses minor code structure issues.

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#livechat#discuss#unfollow

[FIX] l10n_in_hr_holidays: fix sandwich leave warning sign

PR #192071

Coresaas-18.1l10n_in_hr_holidays

The India Time Off screen now shows the sandwich leave warning in the correct layout. This prevents a visual glitch when HR teams configure or review leave requests around weekends.

Original PR description

Steps to reproduce:
- Install India - Time Off
- Create a new time off type in the Indian company and enable sandwich leave
- Create two time offs around the weekends
- The sandwich leave warning appears

Issue:
There is a visual issue with the sandwich leave warning sign.

Cause:
The group contains two columns: one for labeling and one for input.

Solution:
Added colspan="2" to a single div element to occupy the entire space.

task-4435090

#india#time-off#sandwich-leave#ui

[FIX] account: hide purchase tab on product template

PR #193911

Coresaas-18.1account

The product form no longer shows an empty Purchase tab when the Purchase app is not installed. This removes a confusing screen that no longer contains useful settings after the unit-of-measure changes.

Original PR description

Before the refactoring of uom, it was possible to define `uom_po_id`, the uom for purchase that was used for vendor bills. This was the only setting to define in Purchase tab if the Purchase app was not installed.

Since the commit removed this field, the tab became useless and should be removed.

*https://github.com/odoo/odoo/commit/d3fa388cf7c41984b5f7cbc2a81fec3e27a00325

#product#purchase#user interface

[FIX] hr: suppress warning on optimized domains

PR #194731

Coresaas-18.1hr

This fix prevents unnecessary warning messages when employee-related filters have already been prepared for a related employee model. It keeps internal processing quieter and more reliable without changing how users work with employee records.

Original PR description

If the domain is already optimized for another model, the optimize function logs a warning.
While the domain could probably be used as is without requiring the domain to be optimized again (due to the nature of the hr.employee models), we reset the domain completely if the domain has been optimized for another model.

#employees#filters#warnings

[FIX] sale_planning: fix traceback when loading gantt popover

PR #77742

Enterprisesaas-18.1sale_planning

This fixes an error that could appear when users clicked on a shift popover in Planning. Sales-related planning views should now load the shift details reliably, reducing interruptions for scheduling users.

Original PR description

This PR fixes a traceback occurring in planning when clicking on the popover of a shift, due to an async method not being properly overridden.

Task-4506661

#planning#sales#gantt#popover

Before this commit, during a discuss call while sharing screen and enabling camera, the inset card (= small video stream preview in bottom right of call view of the participant, either camera or screen-sharing depending on other stream being main active) was flickering. This happens because each rendering of the call view re-renders the inset, which leads to the perceived flickers from stream being re-rendered. The main cause of re-render comes from `setInset()` that is invoked whenever the `visibleMainCards` getter is called with inset, which is triggered on renderings like mouse-hovering on call view to display the call actions. Even when the inset card is unchanged, `setInset()` produces another object, which forces OWL to re-render the inset component. This commit fixes the issue by having `setInset` reusing the inset data object if the inset to render refers to the same inset session. Task-4484908

Before this PR, leaving a livechat channel from the Discuss app would trigger multiple `action_unfollow` actions: - One initiated by the Discuss app. - Another triggered by the `channel/leave` notification. This PR resolves the issue by ensuring that the `channel/leave` notification does not redundantly trigger an `action_unfollow`. Task-4488437 Additionally, this commit addresses minor code structure issues. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Steps to reproduce: - Install India - Time Off - Create a new time off type in the Indian company and enable sandwich leave - Create two time offs around the weekends - The sandwich leave warning appears Issue: There is a visual issue with the sandwich leave warning sign. Cause: The group contains two columns: one for labeling and one for input. Solution: Added colspan="2" to a single div element to occupy the entire space. task-4435090

Before the refactoring of uom, it was possible to define `uom_po_id`, the uom for purchase that was used for vendor bills. This was the only setting to define in Purchase tab if the Purchase app was not installed. Since the commit removed this field, the tab became useless and should be removed. *https://github.com/odoo/odoo/commit/d3fa388cf7c41984b5f7cbc2a81fec3e27a00325

If the domain is already optimized for another model, the optimize function logs a warning. While the domain could probably be used as is without requiring the domain to be optimized again (due to the nature of the hr.employee models), we reset the domain completely if the domain has been optimized for another model.