#2864 - Tweaks to improve notification settings UX
| Identifier | #2864 |
|---|---|
| Issue type | Trivial issue (does not break functionality) |
| Title | Tweaks to improve notification settings UX |
| Status | Closed (rejected) |
| Handling member | Chris Graham |
| Addon | core_notifications |
| Description | There are some issues when it comes to the UX for notification settings:
*When selecting notification types for items which can be monitored individually (eg. forums), the user automatically receives notifications for all content. I think it's better to also have an option defining what notification settings to set for that content type /when the content is monitored/ opposed to automatically monitoring everything. This tweak isn't that important though as it's just an extension of the screen that pops up when monitoring content; eg. it auto-sets notification settings for quick monitoring. *I feel there should be a way to select multiple notification types for the "typical notification" user option. That way, say if I typically want notifications both in email form and web form, I can do that. *Notification UX can also be improved if staff can set a list of "default" notification settings for new users... perhaps via the notification lockdown screen. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".

Comments
I think adding it would really confuse users more than it would save them time, then we'd need all the extra DB plumbing for storing those preferences.
You seem to be missing here that we already have a setting for members to say whether things are automatically monitored or not.
So the request isn't to add a set of those settings, it is to change the current setting to be individually per content-type.
I think that would be excessive. I don't think a user needs to individually say for each content type what automatic monitoring they want. I also think it would quickly lead to serious UI bloat, so we'd have the implementation quickly followed by a request to define exactly what content-type checkboxes we are going to have there, which would cause even more UI bloat for the admin (to have those options).