-
Notifications
You must be signed in to change notification settings - Fork 10.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change Push Notification logic #1602
Comments
Until this feature gets added, I found a workaround to get notifications regardless of your status. Change the following lines in Rocket.Chat/programs/server/packages/rocketchat_lib.js
The line numbers may change by version. Those line numbers are from 0.34.0. |
Thank you, we have also applied this patch. |
Great, I assume this should make the patch obsolete, which some have applied: #1602 (comment)? |
We need to turn this into a setting |
Thank you very much for this patch. Here are the updated line numbers for version 0.48.2: I agree that this should be configurable. In our case users will frequently leave their desk to visit clients without logging out and they will want to get push notifications anyway. |
Push patch for RC 0.56 in /var/lib/rocket.chat/bundle/programs/server/packages/rocketchat_lib.js line 1821:
line 2000:
|
We should have a setting for |
Users are not getting push notifications, when leaving desk within 5 minutes partially resolves RocketChat#1602
@rodrigok In the end, you just decided not to implement this improvement? |
Currently, the only way you will ever get a push notification is if your connection is considered "away". (This is different from your status. Basically, it's controlled by how long it's been since you last interacted with anything.)
My suggestion is to make the logic instead work like this:
We may also want an option for the current behavior: "Do not send a notification if I have been active in the last X minutes."
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: