canmove, Confirmed users
345
edits
BugzillaImprovements: Difference between revisions
→Remove Severity Field
| Line 95: | Line 95: | ||
=== Remove Severity Field === | === Remove Severity Field === | ||
The "blocker" and "enhancement" severities actually mean something to us currently, but everything inbetween is basically "a bug of some sort" without much actionable difference. I think we should instead have a "blocking trunk" flag which we use to mark bugs which should close the mozilla-central tree, and an enhancement keyword to mark enhancement bugs. -- bsmedberg. | * The "blocker" and "enhancement" severities actually mean something to us currently, but everything inbetween is basically "a bug of some sort" without much actionable difference. I think we should instead have a "blocking trunk" flag which we use to mark bugs which should close the mozilla-central tree, and an enhancement keyword to mark enhancement bugs. -- bsmedberg. | ||
**The Bugzilla project definitely uses this field -- mkanat. | |||
The Bugzilla project definitely uses this field -- mkanat. | * We should still split "enhancement" from "defects" rather than lumping them in the same severity field. In particular the current scheme means we cannot assign "severity" (importance?) to an enhancement, which can range from a minor polish thing to major new functionality. --dveditz | ||
** {{bug|9412}} | |||
We should still split "enhancement" from "defects" rather than lumping them in the same severity field. In particular the current scheme means we cannot assign "severity" (importance?) to an enhancement, which can range from a minor polish thing to major new functionality. --dveditz | |||
=== Remove Platform/Hardware and OS === | === Remove Platform/Hardware and OS === | ||