Closed
Bug 75482
Opened 23 years ago
Closed 23 years ago
RFE: deactivate groups and prevent bugs being added to them
Categories
(Bugzilla :: Bugzilla-General, enhancement, P3)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.14
People
(Reporter: myk, Assigned: myk)
Details
Attachments
(7 files)
7.65 KB,
patch
|
Details | Diff | Splinter Review | |
1.82 KB,
patch
|
Details | Diff | Splinter Review | |
1.73 KB,
patch
|
Details | Diff | Splinter Review | |
803 bytes,
patch
|
Details | Diff | Splinter Review | |
5.76 KB,
patch
|
Details | Diff | Splinter Review | |
12.58 KB,
patch
|
Details | Diff | Splinter Review | |
12.62 KB,
patch
|
Details | Diff | Splinter Review |
There are situations in which a Bugzilla installation may want to "close out" a bug group over time rather than immediately by making it possible for users to continue working on bugs in the group without giving them the ability to extend the life of the group by adding new bugs to it. Since access to the bugs should remain restricted, releasing the bugs back into the wild and deleting the group is not an option. One solution is to add a column to the "groups" table that records whether or not a group is active. An active group can be used in the same way groups are used in Bugzilla today. An inactive group, on the other hand, has certain restrictions on how it can be used that are intended to discourage further use of the group. In particular, it is not possible to add bugs to an inactive group. There may also be other restrictions on that group. I have created a patch that adds UI to the "Edit Groups" screen for de/activating groups and hides the UI in the "Edit Bug" screen for adding a bug to an inactive group. The following SQL command adds the appropriate column to the "groups" table, and I will attach a patch with my changes to bug_form.pl and editgroups.pl: ALTER TABLE groups ADD COLUMN isactive TINYINT NOT NULL DEFAULT 1; -myk
Assignee | ||
Comment 1•23 years ago
|
||
Assignee | ||
Comment 2•23 years ago
|
||
Assignee | ||
Comment 3•23 years ago
|
||
cc:ing people who should know about this bug
Status: NEW → ASSIGNED
Comment 4•23 years ago
|
||
this is a Security Thing (tm) -> 2.14
Target Milestone: --- → Bugzilla 2.14
Comment 5•23 years ago
|
||
Comment 6•23 years ago
|
||
Comment 7•23 years ago
|
||
I should point out that you'll need a patch to post_bug.cgi to stop people from filing new bugs into said groups.
Assignee | ||
Comment 8•23 years ago
|
||
I am about to attach an updated patch that includes the following changes: 1. incorporates Jake's patch for checksetup.pl; 2. patches enter_bug.cgi so it doesn't display inactive groups in the "enter new bug" form; 3. patches post_bug.cgi to throw an error if a new bug is added as a member of an inactive group; (This should never happen unless there is a bug in Bugzilla or the user hacks the "enter new bug" form to try to sneak the bug into the group.) 4. adds a function "GroupIsActive" to globals.pl which returns whether or not a group is active; (This is useful for the post_bug.cgi patch.) 5. modifies my previous patch to form_bug.cgi so the UI for inactive groups does get displayed if the bug is a member of the group. (My previous patch hid the UI for inactive groups for all bugs, but if a bug is a member of a group that gets deactivated, it should still be possible to remove the bug from the group. In fact, it should be encouraged.)
Assignee | ||
Comment 9•23 years ago
|
||
Updated•23 years ago
|
Comment 10•23 years ago
|
||
Can we put this on landfill?
Assignee | ||
Comment 11•23 years ago
|
||
Assignee | ||
Comment 12•23 years ago
|
||
Comment 13•23 years ago
|
||
Based on visual inspection of the patch, and on testing the heck out of it on landfill, looks like it works as advertised. r= justdave Checked in.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 14•23 years ago
|
||
Moving to Bugzilla product
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: Bugzilla 2.11 → unspecified
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
•