Thursday, March 20, 2025
5 changes · saas-18.2
Resolved issues and error corrections
Unread channel threads in the Discuss sidebar now appear at full visibility in compact mode. This makes new activity easier to notice and keeps the display consistent with other unread conversations.
Original PR description
Before this commit, channel threads that are unread had a 75% opacity in the discuss sidebar when the sidebar is compact. When a sidebar item is neither active and has no unread messages, they are…
Before this commit, channel threads that are unread had a 75% opacity in the discuss sidebar when the sidebar is compact. When a sidebar item is neither active and has no unread messages, they are intended to have 75% opacity, so that the active item is easier to spot and they are less distracting compared to message avatars in the selected conversation. This is specific to discuss compact mode because of avatars next to conversation, but also the compact layout shows less of bg of selected item, so the same bg color is not as visible as in expanded mode. This worked for all items but channel threads before this commit. This happens because the feature to but opacity-100% on unread conversations in discuss sidebar relies on `o-unread` classname, but channel thread had `o-item-unread`. There's no reason to have a different classname, thus this commit fixes the issue by using `o-unread`, which makes them reuse the existing style of all other discuss items that have unread messages. Before / After <img width="64" alt="Screenshot 2025-03-20 at 12 10 29" src="https://github.com/user-attachments/assets/60662d82-da39-404d-b3d5-258e5af6618d" /> <img width="61" alt="Screenshot 2025-03-20 at 12 10 55" src="https://github.com/user-attachments/assets/24d16e87-6702-42cb-8416-bf5ef3174b9d" />
Point of Sale orders now correctly clear the customer when a cashier removes them before payment or synchronization. This prevents backend records from keeping an outdated customer, improving order accuracy and reporting.
Original PR description
Steps to reproduce: -------------------------- - Open session in point_of_sale. - Order something with any customer selected. - Now remove the customer and pay. Issue: -------- - The order still have that customer in the backend. Cause: ---------- - When we remove the partner and pay or do any operation which sync order It will have no partner in the order_dict to be written instead of false. So it won't write the partner as the key not found. Fix: ----- - We should have partner_id to be written as false if not there. Task: 4619078
The recruitment app now correctly checks conditions for each applicant when several applicants are processed together. This prevents an error that could interrupt recruitment workflows involving multiple candidates.
Original PR description
As self can contains multiple applicants, it raises an ensure_one error. TASK-ID: 4656015 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website form submissions now keep attached files from being duplicated. This prevents confusion for users and reduces unnecessary duplicate files in the system.
Original PR description
After this commit, the attached files in the form are no longer duplicated. task-4656465 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The appraisal feedback counter now shows the actual number of completed feedback surveys instead of always displaying zero. This helps managers and HR teams quickly see appraisal feedback progress accurately.
Original PR description
In dee57c5a85e26e57159a6eb66de0b2f1f581c64b, which adds prefixes to the states of the model `hr.appraisal`, a search domain on an unrelated model has unfortunately been affected too. This commit fixes the search domain in `_compute_completed_survey_count` which looks at the state of `survey.user_input`, which is not prefixed. Before this commit, the Feedbacks stat button on an appraisal will always show "0 / X", because the filtered state doesn't exist. After this commit, it will show the correct number. Task-id: none