search

RocketChat / Rocket.Chat

The communications platform that puts data protection first.
https://rocket.chat/
Other
40.23k stars 10.42k forks source link

Settings for confirmation for using @all notification on messages #909

Open gmsecrieru opened 9 years ago

gmsecrieru commented 9 years ago

Even though we had a few funny times when someone shoot an @all notification in the middle at the night on the Demo Server, what do you folks think about the idea of adding a settings-based confirmation before using it?

screen shot 2015-01-30 at 3 36 44 pm

Maybe it could be related to rules such as the number of users in the channel and/or number of different timezones etc.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

geekgonecrazy commented 8 years ago

Referencing #1268 as has bounty.

engelgabriel commented 7 years ago

Refs https://github.com/RocketChat/Rocket.Chat/issues/1654

joshuahaber commented 7 years ago

Is it possible to disable the @all functionality completely? If someone tries to send to @all, it doesn't do anything?

MartinSchoeler commented 7 years ago

@joshuahaber can remove the mention-all permission from all users

FaizanZahid commented 5 years ago

+1

rodrigok commented 5 years ago

We already have options to restrict the usage of @all in large rooms.

This issue is more related to an UX improvements with some intelligence advising users when some of the ones that will be notified aren't in work hours.

So I set this as a GSoC idea.

Saibaba1009 commented 3 years ago

@rodrigok hey is this issue is still to be solved can I work on this and do necessary improvements.

atpug22 commented 3 years ago

@rodrigok @engelgabriel is this issue still unsolved then can I work on this??

rodrigok commented 3 years ago

@atpug22 yes, we didn't solve this yet, feel free to propose a solution :)

cgaswin commented 3 years ago

Hello everyone, can someone tell me what changes are you expecting on this issue. Is this issue specific to UI/UX designers?

micksharma commented 3 years ago

Can I work on this bug ?

Akshanshkaushal commented 3 months ago

Hello,

I would like to work on this problem. Let me suggest a fix. When @all is triggered, a confirmation prompt message will be shown based on the number of users and users in specific timezones.

Along with this, there is an option to schedule messages based on timezones. The backend will fetch the different timezones based on who belongs to that group and group people based on timezones. Now users can send messages based on timezones.

for instance, there are 18 people in a group . 9 from India, 3 from Germany, and the rest from USA. So when all is triggered, along with confirmation, there is an option to schedule messages for these 3 different timezones. Based on scheduled messages, they are delivered to people belonging to that timezone.

The solution involves two key enhancements to the notification system:

-->Confirmation Prompt Based on Users and Timezones: 1>When the @all notification is triggered, a confirmation prompt will appear. 2>This prompt will be shown based on the number of users and their respective timezones.

-->Scheduled Messages Based on Timezones: 1>Provide an option to schedule messages according to the users' timezones. 2>The backend will determine the different timezones of users in the group. 3>Users can then send scheduled messages specific to each time zone.