Provides "Do Not Disturb" and "Snooze Notifications"

[lindoelio]

@RocketChat/core

Closes RocketChat/feature-requests#803
Closes #2143
Closes #6418

Provides ability to mute notifications for a time period ("do not disturb" and "snooze notifications") covering both features either on "application level" (for any notifications from all chat subscriptions) or on "channel/room level" (include direct messages subscriptions).

"Do Not Disturb" and "Snooze Notifications" on application level are options available on user's notifications/messages preferences (snoozing all notifications addressed to user, from whatever subscriptions). In addition, this features also can "do not disturb" and/or "snooze notifications" on specific channels (and also shall be combined with behavior defined for "application level").

Setting "Do Not Disturb" and "Snooze Notifications" on Application Level

Setting "Do Not Disturb" and "Snooze Notifications" on Channel Level

[sampaiodiego]

I think the "Do Not Disturb" feature makes more sense on application level (instead of room level). Let's say I'm using Rocket.Chat for work, so I would like to not be disturbed in any room on whole server, and not have to set the same thing on each channel I'm in.

the snooze feature I can see using both application and room levels. but having per room I think it's ok =)

awesome features btw.. thank you

[rodrigok]

I agree with @sampaiodiego do not disturb should be an application level and ask user how long to stay (like the snooze but with one option forever, that eliminates the snooze option)

The same could be made to the room level, but we should call it as mute where you could mute for a certain period of time or forever, like whatsapp does

What do you think?

[graywolf336]

Question - what timezone are the times set in? Are they UTC or the user's timezone?

[lindoelio]

@sampaiodiego and @rodrigok
I should explain better about this features; I will do this on PR description for better comprehension from all guys.

In true, this current PR already covers both features either on "application level" or "channel/room level". So, "Do Not Disturb" feature already works for mute any notifications on a Rocket.Chat instance for that user (who can setup this on yours Notifications/Messagens preferences - that come off by default), besides works also on channel level granularity (combined with user settings for "application level" at the same time). It's exactly what you think that it should be :-)

"Do Not Disturb" and "Snooze Notifications" features also works fine together with implements already merged for mute/hide notifications on our current release, in both granularity level (global/application and channels/rooms).

@graywolf336
It shall set the user's timezone. In this case, moment works on instance's server side for set and get.

I'm waiting for your heavy code review :-P I (and a lot of people on our community) would love see this merged soon!

Thanks for your feedback!

[lindoelio]

Closing for a while... Working on how long to stay "do not disturb" feature, as suggested.

[tassoevan]

Some considerations to refresh this pull request:

1. sendNotificationsOnMessage was deeply modified, specially the afterSaveMessage callback;
2. pushNotificationsFlexTab layout changed a lot, so we need a design review comparing older and newer versions;
3. Other conflicts have easy resolutions.

[pjv]

Please, please figure out how to get this PR merged. DING DING DING.

[samtuke]

We'd also love to see this feature implemented on RocketChat hosted

[sveatlo]

Please, merge this. It's (at least from our perspective) the most important function for a chat application used in a workspace.

[majklovec]

This is really needed in our company, could you please merge that?

[mariohamann]

+1
Please add this one!

[dupinka]

I agree, please add this, this would be extremely useful for our company.

[lequy1010]

That's a good function.
I think do not disturb should be an room level, because when i have lots of room and i want to don't disturb from some room.

[rcerrejon]

no plans to add this feature?

[dancorrigan1]

Much requested feature from my internal users. +1

[nedvedad]

Our team members request this feature almost on daily basis. Implementation would be very much appreciated.

[dusatvoj]

@nedvedad One of the features which is needed AF but it probably will never be merged (bcs there's a lot of changes in master) 😕