Closed
Bug 148069
Opened 22 years ago
Closed 18 years ago
Email interface is not disabled for disabled user accounts.
Categories
(Bugzilla :: User Accounts, enhancement)
Tracking
()
RESOLVED
DUPLICATE
of bug 100953
People
(Reporter: sriram, Unassigned)
Details
I have serveral users that have been disabled, but users still are submitting bugs to these disabled users. I checked out in Bugzilla Documentation & found this... At this time, "Disabled Text" does not prevent a user from using the email interface. If you have the email interface enabled, they can still continue to submit bugs and comments that way. We need a patch to fix this. Is this patch available for 2.14.1?? If yes whats the patch no... If the patch is not yet available what is the target milestone by when this will be available. My Thought on how this should work :- Ideally speaking, Bugzilla should not let users to be disabled if email interface is enabled. The second option could be if users are allowed to be disabled with email interfacing on, then while submitting a bug, it should force the user to enter an address in the ToBox thus ensuring that the bug does not get assigned to a disabled user.. -Sriram-
Comment 1•22 years ago
|
||
Umh... If I understand this correctly, there are actually two bugs here. One is the thing mentioned in the Guide - that email interface (bug_email.pl) doesn't honor the disabledtext, so that even disabled accounts can be used by the account owner. The other is the concept of disabled accounts being assignees (qa contacts, default owners and so on) - truly, I don't think there's anything to prevent assigning bugs to disabled accounts. I'll filed bug 148079 on that, this one seems to cover the email interface thing.
OS: Linux → All
Hardware: PC → All
Comment 2•22 years ago
|
||
This is why we need front-end/back-end separation. =)
Target Milestone: --- → Bugzilla 2.18
Comment 3•20 years ago
|
||
Enhancements which don't currently have patches on them which are targetted at 2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. Consideration will be taken for moving items back to 2.18 on a case-by-case basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Comment 4•20 years ago
|
||
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged enhancement that hasn't already landed is being pushed out. If this bug is otherwise ready to land, we'll handle it on a case-by-case basis, please set the blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Assignee: myk → user-accounts
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
as filed this is WONTFIX. the spirit is bug 100953. *** This bug has been marked as a duplicate of 100953 ***
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•