Closed
Bug 194355
Opened 22 years ago
Closed 20 years ago
delete user operation doesn't clean group mappings
Categories
(Bugzilla :: Administration, task)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.20
People
(Reporter: tom.soderberg, Assigned: Wurblzap)
References
(Blocks 1 open bug)
Details
(Whiteboard: [blocker will fix])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212
If a bugzilla user is delete the group mappings for this user is not
affected/cleared.
Reproducible: Always
Steps to Reproduce:
1. create new user
2. dete this new user
3.
Actual Results:
Sanity check complains
needs following statement to editusers.cgi:
SendSQL("DELETE FROM user_group_map
WHERE user_id=" . $userid);
Comment 1•21 years ago
|
||
Yep, you are indeed correct. What we're waiting on is the ability to make sure
that if a user's ever touched a bug, or if a user's a default owner, don't
delete them.
However, taking them out of all groups that they're in can't really hurt, I think.
So, I think we should take a patch on this one and then work on a better solution.
-M
Status: UNCONFIRMED → NEW
Depends on: bz-references
Ever confirmed: true
OS: Windows 2000 → All
Version: unspecified → 2.17.6
Comment 2•21 years ago
|
||
That would not be sufficient to make a user deletable.
A user should never be deleted if that user has EVER reported or touched a bug.
For practical purposes, the only way a user should be deletable is if the user
was the result of a typo on account creation and has never even logged in.
Yes, the current code blindly (pretty much) just deletes a user from the
profiles table.
The improved code as part of the templatisation on bug#119485 improves this a
lot, and in doing so will fix this bug.
Depends on: 119485
Assignee | ||
Updated•20 years ago
|
Assignee | ||
Comment 4•20 years ago
|
||
Fixed by bug 119485 :)
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•20 years ago
|
Assignee: justdave → wurblzap
Status: REOPENED → NEW
Comment 5•20 years ago
|
||
Resolving with the owner who actually did all the work.
Status: NEW → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Target Milestone: --- → Bugzilla 2.20
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•