Wednesday, February 26, 2025
6 changes · saas-18.1
Resolved issues and error corrections
This update fixes a faulty automated test in the base module so it checks the intended record behavior correctly. It helps keep the test suite reliable and reduces false failures in development checks, with no expected impact on end users.
Original PR description
`test_15_o2m` was trying to check the result of an `in` query with False and False/id, however the id provided was the parent of a leaf, which should not return the parent itself, while the assertion right after checks that the parent is present in the result. The test was passing as with demo data the first record in `leaves` didn't have a parent_id. Runbot Error 135019
This fix prevents loyalty-related product filtering from accidentally hiding regular products in Point of Sale. It makes loyalty behavior more reliable and helps ensure POS tests and workflows reflect the correct available products.
Original PR description
check commit message for description
The mobile navigation bar in Point of Sale and Restaurant Point of Sale now scrolls horizontally as expected. This makes the interface easier and more consistent to use on mobile devices, especially when many navigation items are available.
Original PR description
Before this commit: ========== - Horizontal scroll for a navbar bar is not working as expected in the mobile view. After this commit: ========== - Horizontal scroll for a navbar bar will work fine, ensuring the navbar remains consistent on mobile devices. task-4550203
The HR app now avoids an error when someone tries to archive a new employee record before saving it. This prevents an unexpected interruption and keeps the employee management workflow smoother.
Original PR description
Currently, an exception is raised when a user attempts to archive a new employee before saving. Steps to Reproduce: 1. Install the HR module. 2. Navigate to the Employee Module. 3. Try to archive a new employee before saving. 4. An error occurs. Error: `ValueError Expected singleton: hr.employee() ` This issue occurs when a user tries to archive a new employee before saving because the system expects a default departure date for the employee, which can't be set properly without saving the employee record first. [1] - https://github.com/odoo/odoo/blob/4f58eb9db55c102786010efe3c1fb74edefaf8f3/addons/hr/wizard/hr_departure_wizard.py#L13 This fix resolves the issue by first checking if the employee exists, and then proceeding to find the departure date. sentry-6301787988 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Call participant avatars in Discuss now stay clearer when many people are in a call. Status indicators are hidden in crowded avatar stacks but remain visible where there is enough space, and the participant count is positioned to avoid covering the active avatar in compact mode.
Original PR description
Before this commit, when there's a call in a discuss conversation with many participants and the participants in sidebar are folded as an avatar stack, their short status (e.g. mute, deafen) were…
Before this commit, when there's a call in a discuss conversation with many participants and the participants in sidebar are folded as an avatar stack, their short status (e.g. mute, deafen) were shown below avatar too. This is a problem because the avatar stack is so compact that there's no room to show the short status. This looks quite off. This commit fixes the issue by removing the short status in the avatar stack. To see the call status of participant, we can easily see it by expanding the call participants. When the discuss sidebar is compact, however, it always show a single call participant (= most recently active participant). There's room to show the short status, so it's shown there to help see whether the most recent participant starts screen-sharing or becomes mute/deaf. Before / After <img width="294" alt="Screenshot 2025-02-19 at 17 41 15" src="https://github.com/user-attachments/assets/a23938ba-0cb8-4bb9-ae38-8f7638ebe5d5" /> <img width="297" alt="Screenshot 2025-02-19 at 17 40 24" src="https://github.com/user-attachments/assets/ee545083-dbde-44f3-ba64-95c4d6a8a536" /> ------- This commit also fixes a small issue with the position of "+X" in the avatar stack when sidebar is compact: the "+X" being at the very top and overlapping avatars make sense when the avatar stack is a preview of avatars and the number is more important in this view than the avatars. This is the case in non-compact sidebar mode, as we can easily expand the call participants. In compact mode, however, the active participant is as important if not more than/as the counter. Overlapping the visibility of the single avatar is a problem. Putting the counter at the bottom, while better, hides the counter value so it has some drawbacks. This commit fixes the issue by putting the counter next to avatar in this specific configuration of compact sidebar with call participants. Before / After <img width="67" alt="Screenshot 2025-02-19 at 17 41 09" src="https://github.com/user-attachments/assets/f596e896-6b37-4bc8-b4bd-e92539ebaa67" /> <img width="51" alt="Screenshot 2025-02-20 at 11 08 43" src="https://github.com/user-attachments/assets/88f34855-b02c-4653-8621-63563f0731ed" />
Avatars in the Discuss command palette now display with the correct cropping instead of appearing stretched. This improves visual consistency when users search or mention people using the command palette.
Original PR description
Before this commit, avatars in the discuss command palette (`@` mode in ctrl-k) could have images stretched. This happens due to missing `.o_object_fit_cover`, which is important in all discuss images. Before  After 