You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a bug in the notification message formatting for events when a user changes the avatar,Room Name, or converts a room to a team and vice versa. Specifically, the notification message sometimes appears empty or displays improper wording that does not align with the expected behavior in the Rocket.Chat app. This leads to a confusing user experience when such events are triggered.
Steps to reproduce:
Change the room's avatar.
Change the room's name.
Convert a room to a team.
Convert a team back to a channel.
Observe the notification message in the chat for these events.
Expected behavior:
The notification message should display clear and correct wording corresponding to each event.
For a room avatar change, room name change the message should clearly indicate that the room avatar has been changed or room name has been changed.
For room conversion events (room-to-team and team-to-channel), the message should clearly indicate the conversion, e.g., "converted #roomName to team" or "converted #roomName to channel".
The message should not be empty under any of these conditions.
Actual behavior:
The notification message appears empty for the avatar change or room's name conversion events.
The displayed wording does not match the expected phrases and is inconsistent with the Rocket.Chat app.
This bug affects clarity and usability for users monitoring system events through notifications.
The text was updated successfully, but these errors were encountered:
Description:
There is a bug in the notification message formatting for events when a user changes the avatar,Room Name, or converts a room to a team and vice versa. Specifically, the notification message sometimes appears empty or displays improper wording that does not align with the expected behavior in the Rocket.Chat app. This leads to a confusing user experience when such events are triggered.
Steps to reproduce:
Expected behavior:
Actual behavior:
The text was updated successfully, but these errors were encountered: