Opened 17 years ago
Last modified 9 years ago
#6173 new enhancement
Allow accounts to be disabled, such that they no longer receive email notifications
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | next-major-releases |
Component: | notification | Version: | devel |
Severity: | major | Keywords: | |
Cc: | dirk.moebius@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
When a developer or other Trac user becomes inactive in a project, it would be nice to be able to simply 'lock' their account, preserving as much information as possible. Because otherwise they'll be receiving email notifications for every bug they've reported, etc.
Workarounds, and why they're undesirable:
- Modify every ticket they've reported. Error-prone and tedious, plus minor data loss.
- Modify the configuration of the mail server to alias the login to /dev/null. Not always practical, and sometimes you still want non-automated emails to go through to them.
DELETE FROM session WHERE sid=:developername AND var_name='email';
Someone needs to look this code up, and if the schema changes it might break. Also, encouraging people to mess with the database internals is probably a bad idea in the long term.
If there's a way for Trac to determine whether the auth system has locked an account, relying on that would probably be the most elegant solution.
Attachments (0)
Change History (11)
comment:1 by , 17 years ago
Component: | general → notification |
---|---|
Owner: | changed from | to
Severity: | normal → minor |
Version: | → devel |
comment:2 by , 17 years ago
comment:3 by , 17 years ago
Cc: | added |
---|
Wouldn't it suffice to simply blank out their email addresses?
comment:4 by , 16 years ago
Priority: | normal → high |
---|
Even users who have had their Trac accounts deleted continue to receive Trac Notifications. Not being able to unsubscribe from a ticket, ever, seems like it should be a big deal. I have removed always_notify_updater from my trac.ini (which actually notifies all updaters, ever) and cleaned all of the reporter and owner fields of deleted users which has gotten around most of my problems (although I would like to be able to use the always_notify_updater functionality one day). Unfortunately (as mentioned above) this is a tedious task which destroys data. Is there any movement on this issue? Not going to put my email address on this comment for obvious reasons!
Thanks, Joe
comment:5 by , 16 years ago
Priority: | high → highest |
---|---|
Severity: | minor → major |
This has been a become a big problem on my project as well. No way to unsubscribe from Trac Notifications?!?!?!
comment:7 by , 16 years ago
Priority: | high → normal |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
If usernames are used in ticket fields (reporter, owner, CC), it should be sufficient to remove the e-mail address for the account. This doesn't require direct database manipulation if th:AccountManagerPlugin is installed.
If e-mail addresses were used directly in ticket fields (no user accounts), this would require the batch ticket modification functionality (#525).
comment:8 by , 16 years ago
Milestone: | → 0.13 |
---|---|
Resolution: | wontfix |
Status: | closed → reopened |
I don't think this should be closed yet. A reworked Notification subsystem + to-be-implemented User Directory service should deal with this situation in a better way. Somehow.
comment:10 by , 9 years ago
Owner: | removed |
---|---|
Status: | reopened → new |
comment:11 by , 9 years ago
Happy to see this tickets was recently revived.
For my implementation, removing inactive users from the dropdown lists is my highest priority.
One additional thing that might be nice is to filter the 'assign to' dropdown list so that disabled users don't appear.