Saturday, November 30, 2024
3 changes
1 change
Resolved issues and error corrections
Helpdesk teams can now only include members from the same company as the team. This prevents tickets from being assigned to users who cannot access or see them, improving assignment accuracy in multi-company setups.
Original PR description
[FIX] heldepsk: Team members should be from the team company. Bug: You can add a Team Member from another company to a helpdesk team. Steps to reproduce: - Create two Companies, one User in each company - In the Helpdesk Team of Company 1 > Automatic Assignement > add also User from Company 2 - Connect to User 2 > he doesn't see the Tickets even if he is assigned to it Solution: - filter member_ids by the current company task-4207465
2 changes
Resolved issues and error corrections
Incoming call invitation pop-ups now keep a consistent dark background with white text, instead of appearing transparent or switching to a bright style in dark mode. This makes call notifications easier to read and reduces visual discomfort for users using dark theme.
Original PR description
Call invitation was transparent because text-bg-900 is a backend-specific classname style. As a result, the pop-up had no bg-color. Also the background color and text looks good in white theme: black background with white text. This matches the colors in the call view. In dark theme the colors were inverted: white background and black text. This is unintentional, because this doesn't match call view color that is black color and white text in dark theme too. Also the main advantage of dark theme is to put less eye strain and the inverted colors in dark theme were actually more eye-straining than white theme. This commit fixes the issue by putting specific color in CSS. These colors should not change with theme: dark theme should keep dark background and white text. task-4354214
LinkedIn hashtag links generated from social posts now use LinkedIn's current link format. This helps ensure hashtags, including edge cases like short or mixed formats, open correctly for users viewing LinkedIn content.
Original PR description
With the current links generated for the hashtags in Linkedin, there's a few corner cases that are not being handled by Linkedin side as we expect it to (ex #FLD), so from 18.0 onwards we should follow the same formatting Linkedin is using nowadays. Previous link: https://www.linkedin.com/feed/hashtag/FLD2024 Link after the change: https://www.linkedin.com/feed/hashtag/?keywords=FLD2024 In the previous links you can see the differences between them. opw-4326960