Please create a new product called Tracking in the Other classification. Description of this product "for tracking bugs that cross multiple products" Also please add the component "Kilimanjaro" to that Product with the description "tracking bugs for the Kilimanjaro project" with Kilimanjaro linked to https://wiki.mozilla.org/Kilimanjaro We will continue to use this Tracking product for future cross-product tracking efforts including the follow-up to k9o.
this shouldn't be a problem; however there's a few other details we'll need in order to set this up. please see https://wiki.mozilla.org/BMO/Requesting_Changes#Products
The name of the product: Tracking The classification: Other A longer description: For tracking bugs that cross multiple products and services The initial list of components, with their info (see below): Kilimanjaro A longer description: tracking bugs for the Kilimanjaro project https://wiki.mozilla.org/Kilimanjaro Any flags (bug and/or attachment): none The initial list of versions, with their info (see below): empty or default or --- The initial list of target milestones, with their info (see below): empty or default or --- The security group(s) bugs should be classified under: disable this flag or use core security (or security core, not sure which it's named.) The number of votes needed to confirm a bug: disabled. Is this something you can get done today? We've got scores of people waiting.
(In reply to Asa Dotzler [:asa] from comment #2) > Is this something you can get done today? We've got scores of people waiting. i'll start creating it now.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
How does this differ from Core :: Tracking?
(besides being a product instead of a component)
(In reply to Reed Loden [:reed] (very busy) from comment #5) > How does this differ from Core :: Tracking? from the name i'd expect core::tracking to be limited to core, or at best, core/firefox/toolkit meta bugs. kilimanjaro needs to track issues across more products than that.
While Core does live inside of most of our client software products, so there's some (though not great) justification for using it to track bugs across client software components or products, it's just completely the wrong place to track cross-product cross service issues or programs. Something like Kilimanjaro lives above all of the other products (or at least beside them) and certainly not inside one of them. Verfied at https://bugzilla.mozilla.org/enter_bug.cgi?product=Tracking Thanks Glob!
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.