Skip to content
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

Reorganise Advanced Notifications in to Global Notifications, Keywords and Mentions, Other #3646

Closed
langleyd opened this issue Jul 7, 2021 · 2 comments · Fixed by #3673
Closed
Assignees

Comments

@langleyd
Copy link
Member

langleyd commented Jul 7, 2021

This issue is to re-organise Account Settings > Notifications > Advanced Notifications in to Global Notifications, Keyword and Mentions and Other

The only change in functionality is that rather than 3 options for off, silent ,noisey there will just be a checkbox for on/off states with the on meaning `noisey.

This shows the new grouping under the Account Settings > Notifications:
image

Global Notifications
image

Mentions and Keywords
image

Other
image

@langleyd langleyd added the T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements label Jul 7, 2021
@langleyd langleyd self-assigned this Jul 7, 2021
@langleyd langleyd removed the T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements label Jul 9, 2021
@langleyd langleyd changed the title Reorganise Advanced Notifications into Global Notifications, Keywords and Mentions, Other Reorganise Advanced Notifications in to Global Notifications, Keywords and Mentions, Other Jul 14, 2021
@langleyd langleyd linked a pull request Jul 15, 2021 that will close this issue
@AnisTaluqdar
Copy link

What about if someone replies to me? It would be great if there have an option to notify reply text.

@matthijskooijman
Copy link

The only change in functionality is that rather than 3 options for off, silent ,noisey there will just be a checkbox for on/off states with the on meaning `noisey.

What's the rationale for this change?

I was very much using these options, so I can get noisy notifications for one-on-one rooms and mentions, and silent notifications for other rooms (that typically have too much activity to be noisy, but I do want to get a notification on the screen for their activity). This configuration was also the default, not sure if that has also changed? I recall reading an issue where this was discussed as the preferred default configuration to not overload people with noisy notifications by default. I can't quite find it again, but it does suggest that I'm not the only one that wants to use silent notifications.

It seems you can still configure silent notifications through element web, but I'm slightly worried that if this setting is removed in the Android version intentionally, it will also get dropped from the web version.

What's also a bit weird now, is that the Element Android now allow configuring "silent" and "noisy" (and "call") notification profiles. It does make sense to have these, since even if Element Android does not allow configuring silent notifications, they can be configured (through push rules) from other clients, so Element Android must be able to handle silent notifications I guess. But without a way to configure a notification as "silent" or "noisy", I expect this will be confusing to users (which will not know which of these two will be used when they put a checkbox for some notification category).

Also, anyone that still has silent notifications configured will just see the checkbox, and might end up being confused why some notifications are silent and some are noisy, since both will just have a checkbox. AFAICS, if they uncheck and recheck the checkbox, things will change from silent to noisy, which is also quite unexpected (I would expect that unchecking and rechecking a checkbox would restore the same state as before).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants