View Issue Details

IDProjectCategoryView StatusLast Update
5278Composrcore_notificationspublic2023-02-12 00:26
ReporterPDStig Assigned ToPDStig  
PrioritynormalSeverityfeature 
Status closedResolutionno change required 
Summary5278: Change the behaviour of notification lockdown to force the default value
DescriptionIf the notification defaults screen is used together with the notification lock-down screen, the notification lock-down screen requires redundant mirroring and can be improved to be more useful.

The current behaviour: You can either let the member decide which notification media they want for each type, or you can lock down all media for a certain type and specify which ones are enabled versus disabled.
Example: If I lock down to "instant e-mail", then all media for that notification type becomes non-editable by the member, and instant e-mail is the only one enabled.

Proposed changed behaviour: Locking down notifications determines which ones are forced to the default value.
Example, if I lock down "instant e-mail", then the instant e-mail medium for that notification type, and *only* the instant e-mail medium for that type, becomes non-editable by members, and its setting reflects / is forced to the default value (which can be changed on the notification defaults screen). Members can still choose the other media for that type, such as digests and web notifications.

Use case: Many servers have a limit on the number of e-mails that can be sent per hour. So it would be great if members could lock down instant e-mails for a variety of notification types to reduce the number of e-mails being sent... but to allow members to still have their choice of other types, like digests and web notifications.
TagsNo tags attached.
Attach Tags
Time estimation (hours)2
Sponsorship open

Sponsor

Date Added Member Amount Sponsored

Relationships

has duplicate 1869 Not AssignedGuest Notification lockdown expansion to include selecting what options are available 

Activities

PDStig

2023-02-12 00:26

administrator   ~7911

We are sticking with the original duplicate issue by combining the two notification screens together.

Issue History

Date Modified Username Field Change
2023-02-10 17:07 PDStig New Issue
2023-02-10 17:09 PDStig Relationship added has duplicate 1869
2023-02-11 20:24 Chris Graham Description Updated
2023-02-12 00:26 PDStig Assigned To => user4172
2023-02-12 00:26 PDStig Status Not Assigned => Closed
2023-02-12 00:26 PDStig Resolution open => no change required
2023-02-12 00:26 PDStig Note Added: 0007911