Closed
Bug 43619
Opened 24 years ago
Closed 22 years ago
caneditgroupmembers and creategroups are not honored correctly in editgroups.cgi
Categories
(Bugzilla :: Administration, task, P2)
Bugzilla
Administration
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: justdave, Assigned: justdave)
References
Details
(Whiteboard: code)
Everything in editgroups.cgi right now is based on the 'creategroups' priv.
Users should also be allowed in if they have caneditgroupmembers, but just not
allowed to Add, Edit, or Delete groups (just edit members). Also, if the user
has blessgroupset privs for any groups, they should be allowed in, and only able
to see the groups they have access to.
Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Comment 1•24 years ago
|
||
Should editgroupmembers get them into editgroups.cgi? I would think that that
would get them into editusers.cgi, with an interface similar to when you've got
the bless group bit turned on for one or more groups... In fact, it sounds,
from the description, like someone in the editgroupmembers group should be
considered to have the bless group bit turned on for each group they're in. Am
I reading this wrong?
Assignee | ||
Comment 2•24 years ago
|
||
I think you've got it. That's what I was thinking. There's a number of privs
defined right now that don't really mean anything. That being one of them.
That's what I files this bug for, to remind us when we got back to working on
those that it still didn't cover everything it was supposed to.
Updated•23 years ago
|
Target Milestone: --- → Bugzilla 2.14
Updated•23 years ago
|
Whiteboard: code
Assignee | ||
Comment 3•23 years ago
|
||
No clue what I was thinking here, unless we wanted to add that group. This could
probably be handled by checking blessgroupset or editusers... certainly not a
2.14 blocker.
Depends on: 68022
Target Milestone: Bugzilla 2.14 → Bugzilla 2.16
Updated•23 years ago
|
Priority: P3 → P2
Updated•23 years ago
|
Component: Bugzilla → Administration
Product: Webtools → Bugzilla
Version: other → unspecified
Assignee | ||
Comment 4•23 years ago
|
||
We are currently trying to wrap up Bugzilla 2.16. We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut. Thus this is being retargetted at 2.18. If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
Comment 5•22 years ago
|
||
This is already covered. Anyone who can bless any group can use editusers to
do so.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Target Milestone: Bugzilla 2.18 → ---
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
•