View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005443 | Composr | core_cns | public | 2023-11-14 05:57 | 2024-03-30 03:52 |
Reporter | Patrick Schmalstig | Assigned To | Patrick Schmalstig | ||
Severity | Feature-request | ||||
Status | resolved | Resolution | fixed | ||
Product Version | |||||
Fixed in Version | |||||
Summary | 0005443: Forced email and web notification when staff edit a member's notification settings | ||||
Description | To help prevent staff abuse (e.g. turning off certain notification settings for a member so that they can then change critical settings / SU into their account undetected), there should be a hidden notification type (or at least make it visible, but not editable) that will email and send a web notification to a member whenever someone changes their notification settings. Ideally, the notification should also list what notification settings were changed, and who changed them. | ||||
Additional Information | Alternatively, if we do not want this being a hidden / forced notification, we could classify changes to a member's notification settings as "high impact" and include it as part of the "high impact change" notification. | ||||
Tags | Roadmap: v11 | ||||
Time estimation (hours) | |||||
Sponsorship open | |||||
related to | 0005442 | closed | Patrick Schmalstig | New notification type to let users know when staff SU'd into their account |
|
Actually enable_notifications and disable_notifications were very confusing for API names because enable_notifications could disable them, and disable_notifications really means "reset to default". I renamed these API calls as follows: enable_notifications -> set_notifications disable_notifications -> reset_notifications |
|
I went the route of treating notification edits as high-impact changes. They will be sent out just like high-impact changes for username, password, etc. |
Date Modified | Username | Field | Change |
---|---|---|---|
2023-11-14 05:57 | Patrick Schmalstig | New Issue | |
2023-11-14 05:57 | Patrick Schmalstig | Status | non-assigned => assigned |
2023-11-14 05:57 | Patrick Schmalstig | Assigned To | => Patrick Schmalstig |
2023-11-14 05:57 | Patrick Schmalstig | Relationship added | related to 0005442 |
2023-11-14 05:58 | Patrick Schmalstig | Tag Attached: Roadmap: v11 | |
2023-11-14 05:59 | Patrick Schmalstig | Description Updated | View Revisions |
2023-11-14 06:00 | Patrick Schmalstig | Description Updated | View Revisions |
2024-01-28 22:55 | Patrick Schmalstig | Note Added: 0008266 | |
2024-01-28 23:40 | Patrick Schmalstig | Status | assigned => resolved |
2024-01-28 23:40 | Patrick Schmalstig | Resolution | open => fixed |
2024-01-28 23:40 | Patrick Schmalstig | Note Added: 0008267 | |
2024-03-30 03:28 | Patrick Schmalstig | Project | Composr alpha bug reports => Composr |
2024-03-30 03:52 | Patrick Schmalstig | Category | General / Uncategorised => core_cns |