Closed
Bug 181589
Opened 23 years ago
Closed 22 years ago
Add mass-group-edits to editgroups
Categories
(Bugzilla :: Administration, task, P1)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.18
People
(Reporter: bugreport, Assigned: bugreport)
References
Details
Attachments
(2 files, 4 obsolete files)
|
8.30 KB,
patch
|
justdave
:
review+
|
Details | Diff | Splinter Review |
|
1012 bytes,
patch
|
timeless
:
review+
|
Details | Diff | Splinter Review |
To assist admins with sites moving from old (2.16 and prior) groups to the new
implicit groups where regexps are continuously applieed, editgroups needs some
new functions.
1) Remove all explicit memberships from this group
2) Remove all explicit memberships who are covered by the regexp from this group
Naturally, both of these need a very serious confirm screen.
| Assignee | ||
Updated•23 years ago
|
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.18
Comment 1•23 years ago
|
||
despite this really being an enhancement, I'm setting the severity on this to
blocker. I will not call Bugzilla "version 2.18" without this feature.
Severity: enhancement → blocker
Priority: P3 → P1
Comment 2•22 years ago
|
||
Dave: your last comment implies that this is really important. Do we need it for
the b.m.o. upgrade?
Gerv
Comment 3•22 years ago
|
||
b.m.o won't need it. But I'll still hold the blocker status for 2.18.
Comment 5•22 years ago
|
||
just to point out to any involved parties, this is still a 2.18 blocker. (2.18
is coming up rather soon now)
| Assignee | ||
Comment 6•22 years ago
|
||
I have been short on time lately. I won't minf if someone wants to work on this.
| Assignee | ||
Comment 7•22 years ago
|
||
To unblock 2.18.....
How about doing this with a hyperlink near the regexp in the editgroups UI. The
hyperlink would be "<a>remove</a> users matching this expression from the group
(they will still have access so long as they continue to match this expression)"
If clicked, it would bring up a confirm screen.
It's not the prettiest approach, but it would work.
Comment 8•22 years ago
|
||
Removing dependancy on 190222 (templatize editgroups.cgi), we need this bug for
2.18 and 190222 isn't targetted until 2.20. We will just have to roll these
changes into the template version.
No longer depends on: 190222
Comment 9•22 years ago
|
||
This patch adds the UI to editgroups.cgi and adds a confirmation screen too.
There's a small bug elsewhere in editgroups.cgi that is fixed as well (proper
html quoting of a hidden form field). Hooks are in place (marked with "# JOEL:
HERE") for the actual group removal logic to be added.
| Assignee | ||
Comment 10•22 years ago
|
||
Attachment #144392 -
Attachment is obsolete: true
| Assignee | ||
Updated•22 years ago
|
Attachment #144447 -
Flags: review?
Comment 11•22 years ago
|
||
In looking at this patch. Maybe the Remove Explicit Members in the Regular
Expression button should be removed if the regex field is empty. When I click on
the button when the field is empty, I get in the next screen,
This option will remove all users included in the regular expression: from group
foo.
| Assignee | ||
Comment 12•22 years ago
|
||
WRT comment 11: We'd have to use javascript to do that (I hate javascript!)
because the user could change the regexp and then click the button.
Alternately, we could have the confirm page just point out that there is nothing
to do. (or both?)
Comment 13•22 years ago
|
||
Maybe this is best done from a page that doesn't let you edit the regexp? Like
the main group list page when you initially go to editgroups.cgi?
| Assignee | ||
Updated•22 years ago
|
Attachment #144447 -
Flags: review?
| Assignee | ||
Comment 14•22 years ago
|
||
OK, confirm screen handles case of empty regexp
Attachment #144447 -
Attachment is obsolete: true
| Assignee | ||
Updated•22 years ago
|
Attachment #144578 -
Flags: review?
Comment 15•22 years ago
|
||
I can't review this as I don't understand groups... but my comment is that I
also don't understand the need for it or what it does from the text in the .cgi.
I suggest that either documentation or more explanation are probably required...
Gerv
Comment 16•22 years ago
|
||
justdave: I think this would be pretty confusing to have on the main editgroup
page, since it specifically edits a single group, not all of them at once.
Comment 17•22 years ago
|
||
maybe it should prompt you for a group to remove people from after you choose it
then. Or maybe the text around the link on the group edit page should state in
the text which regexp will be used for the removal...
| Assignee | ||
Comment 18•22 years ago
|
||
The current patch already does use the new regexp. It is implemented as a
submit button.
The confirm page already does show the regexp that is about to be used.
| Assignee | ||
Comment 19•22 years ago
|
||
Shows who is being removed
Attachment #144578 -
Attachment is obsolete: true
| Assignee | ||
Updated•22 years ago
|
Attachment #144842 -
Flags: review?(justdave)
| Assignee | ||
Updated•22 years ago
|
Attachment #144578 -
Flags: review?
| Assignee | ||
Comment 20•22 years ago
|
||
Attachment #144842 -
Attachment is obsolete: true
| Assignee | ||
Updated•22 years ago
|
Attachment #144842 -
Flags: review?(justdave)
| Assignee | ||
Updated•22 years ago
|
Attachment #144843 -
Flags: review?(justdave)
Updated•22 years ago
|
Attachment #144843 -
Flags: review?(justdave) → review+
| Assignee | ||
Updated•22 years ago
|
Flags: approval?
Comment 21•22 years ago
|
||
This needs documentation and good coverage in the upgrading section of the
release notes.
Flags: documentation?
Flags: approval?
Flags: approval+
Updated•22 years ago
|
Blocks: bz-2.18-relnotes
| Assignee | ||
Comment 22•22 years ago
|
||
Checking in editgroups.cgi;
/cvsroot/mozilla/webtools/bugzilla/editgroups.cgi,v <-- editgroups.cgi
new revision: 1.32; previous revision: 1.31
done
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•21 years ago
|
Flags: documentation2.18?
Comment 23•20 years ago
|
||
Attachment #207900 -
Flags: review?(documentation)
Attachment #207900 -
Flags: review?(documentation) → review+
Comment 24•20 years ago
|
||
Documentation:
tip:
Checking in docs/xml/administration.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/administration.xml,v <-- administration.xml
new revision: 1.55; previous revision: 1.54
done
2.20:
Checking in docs/xml/administration.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/administration.xml,v <-- administration.xml
new revision: 1.50.2.3; previous revision: 1.50.2.2
done
2.18.4:
Checking in docs/xml/administration.xml;
/cvsroot/mozilla/webtools/bugzilla/docs/xml/administration.xml,v <-- administration.xml
new revision: 1.34.2.14; previous revision: 1.34.2.13
done
Flags: documentation?
Flags: documentation2.20+
Flags: documentation2.18?
Flags: documentation2.18+
Flags: documentation+
Updated•13 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
•