Closed Bug 62551 Opened 24 years ago Closed 23 years ago

Hide unused components, rather that deleting

Categories

(Bugzilla :: Administration, task, P3)

Tracking

()

VERIFIED DUPLICATE of bug 77193

People

(Reporter: hansoneric, Assigned: CodeMachine)

Details

In my company our product changes quiet abit over just 6 months, as such components are created and dropped. The reason for dropping are aesthetic and functional, we have alot (bold) of components and if we didn't drop the dead ones people might misassign bugs, wastes time, etc. Since we have deleted components the bugs still stick around, but cause sanity check errors because they have components that no longer exist. I am not sure if this is because I updated our bugzilla from 2.4 to 2.10 or what. Before we had 800 bugs, with the bug id at 1700, after the upgrade a bunch of "missing" bugs appeared, we now have 1700 bugs, but some of the bugs are really wierd, have to manually close through mysql commands, bugzilla is sorta wierded out by the missing component deal. So, if this happens normally, I was thinking it would be a good idea to be able to "Retire" components. Basically they would still exist in some master list, but they would _not_ show up as choices when submitting a bug or even querying a bug (this last might be another option). Perhaps a "Buried" component doesn't show in query or submit, but a "Retired" component would show in a query screen.
Hey, Myk, weren't you already working on something like this under a different bug number?
Target Milestone: --- → Future
Moving to new Bugzilla product, and taking as a part of my refactoring work for 2.16. Not sure about hiding stuff on the query page though ...
Assignee: tara → matty
Blocks: 97706
Component: Bugzilla → Administration
OS: Linux → All
Product: Webtools → Bugzilla
QA Contact: matty → jake
Hardware: PC → All
Target Milestone: Future → Bugzilla 2.16
Version: other → unspecified
Status: NEW → ASSIGNED
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
other bug is newer, but it has more discussion. *** This bug has been marked as a duplicate of 77193 ***
No longer blocks: 97706
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
clearing target milestone on invalid/duplicate/worksforme/wontfix bugs so they'll show up as untriaged if they get reopened.
Target Milestone: Bugzilla 2.18 → ---
Verified dupe
Status: RESOLVED → VERIFIED
QA Contact: jake → default-qa
You need to log in before you can comment on or make changes to this bug.