Monday, March 24, 2025
5 changes · saas-18.2
Resolved issues and error corrections
Automated actions that add or remove followers now receive the correct generated name when using the generic follower action type. This prevents confusing or incorrect labels in automation setup, making it easier for users to identify and manage these actions.
Original PR description
Before this commit the server actions automated naming was not properly working for server actions of type add/remove followers in case of a 'generic' followers action type. This commit fixes this issue (introduced with [1]) [1] https://github.com/odoo/odoo/pull/190709
This fixes an automated test for self-order online payments so it works whether or not demo data is installed. It helps keep the validation pipeline reliable without changing customer-facing behavior.
Original PR description
- Fix test `test_online_payment_self_pay_after_meal_table` that was failling when no demo data was installed. - To fix this issue, we now use a table that exist with or without demo data. - This test was introduced here : https://github.com/odoo/odoo/pull/201294 - runbot error: 161250 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The chat typing indicator now matches the conversation background instead of showing a mismatched grey strip. This improves visual consistency and makes chat windows clearer, especially when using dark mode.
Original PR description
Before this commit, when someone is typing in conversation in a chat window, the "is typing" notification has a `.bg-view`. Problem is that `.bg-view` doesn't match the conversation bg, especially in dark theme where the conversation bg is dark and this is greyish. In chat window this takes the whole width, making it hard to distinguish the rounded rectangle shape of chat window. This commit fixes the issue by replacing the `.bg-view` to `.bg-inherit`, so that the text bg color of "is typing" matches the conversation bg. Before / After  
This fix improves the visual alignment of badges and action buttons in the Discuss sidebar, including both expanded and compact views. Users get a cleaner, more consistent messaging navigation experience with no change to functionality.
Original PR description
Before / After (expanded) <img width="303" alt="Screenshot 2025-03-20 at 12 21 24" src="https://github.com/user-attachments/assets/bc6c0841-aec6-4cf4-8ed8-6cee26b53a9a" /> <img width="301" alt="Screenshot 2025-03-20 at 12 19 22" src="https://github.com/user-attachments/assets/82225946-0b90-4c84-b5c9-77f0c92065a9" /> Before / After (compact) <img width="63" alt="Screenshot 2025-03-20 at 21 48 44" src="https://github.com/user-attachments/assets/2ddff447-d06a-462b-b4b0-0a725e65b100" /> <img width="59" alt="Screenshot 2025-03-20 at 21 47 22" src="https://github.com/user-attachments/assets/c08aa09a-be62-4800-b1d5-4c8b705f098c" />
Appraisal analysis reports now use the same status values as the main appraisal records. This makes grouping by status and filtering by state work correctly in reporting views, helping users analyze appraisal progress reliably.
Original PR description
Issue: cannot groupby status on appraisal analysis neither filter by state in graph view Solve: update the state field values of report to match the original model Task: 4653149