Wednesday, May 28, 2025
4 changes · saas-18.2
Resolved issues and error corrections
Pinned message cards in Discuss now use a lighter border so they blend better with surrounding conversation items. This makes the interface feel more consistent and less visually distracting for users.
Original PR description
Was using default `.border-secondary` which is too strong compared to other discuss items.
The Discuss app now shows a subtle separator above its main area instead of hiding it entirely or using a line that draws too much attention. This improves visual balance while keeping the interface clear for users handling many messages and items.
Original PR description
The default separator color of control panel is too strong, which doesn't fit well in discuss app that has a lot of items that needs enough attention. This was overridden to remove it completely, but now that many work as been done to adjust the right balance of color in discuss app, this separator can be shown at a reduced opacity.
This fixes a small visual spacing issue in Mail conversations where a regular message could appear too close to a following notification, such as a live conference notice. The change makes message lists easier to read while keeping the layout compact.
Original PR description
Before this commit, visual of a message without reactions just above a notification like "started a live conference" looked slightly off. This comes from lack of spacing between them. This commit fixes the issue by specifically adding minimal spacing in-between message without reaction and the notification in the message list. The spacing of message bubbles and notification is intentionally small to be efficient with space and add only when desired. When a message has a reaction, there's already bottom spacing so there's no need to add even more. As a reminder, the bottom spacing on reaction helps to see which message this reaction it is attached to. 
Belgian payroll slip generation has been corrected to avoid an error when multiple worked-day entries are present. This helps payroll teams generate payslips reliably without manual workaround or interruption.
Original PR description
We get a traceback when trying to generate pyslip because we try to read number_of_hours from a recordset containing more than one record. So we are now taking the max of the records.