Closed
Bug 43612
Opened 25 years ago
Closed 19 years ago
User/group maintenance needs to be more robust/easier to use
Categories
(Bugzilla :: Administration, task, P3)
Bugzilla
Administration
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: justdave, Unassigned)
References
Details
(Keywords: meta)
Since I've been working on editgroups.cgi a little bit, I've discovered that it
and editusers.cgi really have a lot of interoperability concerns, and could
really use a lot of enhancement to make it useful to the average Bugzilla
maintainer.
I don't intend to do this all by myself, I'm just making an attempt to coordinate
making this happen. If anyone wants to help out, feel free. There are numerous
small tasks that need to be done to accomplish this. I am going to set up this
bug as a tracking bug to coordinate the effort, and will be marking additional
bugs as dependencies as I run across things that affect this.
If you are interested in helping out, click on the Show Dependency Tree link
above, to see the list of things that need to be worked on.
Reporter | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Updated•24 years ago
|
Severity: normal → enhancement
Target Milestone: --- → Bugzilla 2.16
Updated•24 years ago
|
Component: Bugzilla → Administration
Product: Webtools → Bugzilla
Version: other → unspecified
Reporter | ||
Comment 1•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
Reporter | ||
Comment 2•21 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
Reporter | ||
Comment 3•21 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
Reporter | ||
Comment 4•20 years ago
|
||
Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist. This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it. If you
are dealing with this bug, please assign it to yourself.
Assignee: justdave → administration
Status: ASSIGNED → NEW
QA Contact: mattyt-bugzilla → default-qa
![]() |
||
Comment 5•19 years ago
|
||
Old meta-bug which got no attention at all. Doesn't make sense to keep it open except polluting our queries. We did huge improvements in these fields meanwhile already.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•