Every component in every product should have its own tracking bugs. Now, the information of the component is lost, thus making hard to find them. This bug is quite urgent, because the more we wait, the more there will be tracking bugs: and there is no automatic way to restore their component.
Not a software problem. ->Mozilla.org
Assignee: justdave → asa
Component: Bugzilla-General → Bugzilla: Keyword & Component Changes
Product: Bugzilla → mozilla.org
QA Contact: matty → timeless
Version: 2.15 → other
Tracking is already a keyword, it doesn't need to be a severity.
we already have that, use 'meta' or 'scheduled'. however the tracking component is used by things that don't fit in a single component and I haven't found any problem with that usage. As for changing tracking to a severity, I'm absolutely opposed, you can have a tracking bug that is critical or a tracking bug that is trivial, moving tracking into the severity field loses that information.
I agree with Timeless' first and third points, but his second point applies to any bug that is hard to classify, not just metabugs, so I don't think tracking is a necessary component.
Many of the bugs in the "tracking" component are extremely miscellaneous, e.g. shaver's "futured bugs with patches" bug, or "ship 1.0" -- those seem appropriate. But others are clearly component-specific and probably should have stayed in the component with a 'meta' keyword. Peter's right that "tracking" bugs aren't the only miscellaneous things we have; all the truly misc. bugs should go in Browser-General. "Tracking" can go, it's just going to suck in things that better belong elsewhere. stats as of now: 183 "Tracking" bugs 437 "Browser-General" bugs 576 bugs with "meta" keyword 0 bugs with "scheduled" keyword
tracking is not a severity and I'm not going to make it one.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WONTFIX
vrfy wontfix [moving tracking into severity field]
Status: RESOLVED → VERIFIED
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.