| 2005-06-03 00:00:00 |
Matthew Paul Thomas |
bug |
|
|
added bug |
| 2005-11-02 20:04:50 |
Brad Bollenbach |
malone: status |
New |
Accepted |
|
| 2005-11-02 20:04:50 |
Brad Bollenbach |
malone: assignee |
|
bradb |
|
| 2005-12-01 16:38:47 |
Matthew Paul Thomas |
description |
Malone currently includes a Severity field. In Bugzilla, this field lets the reporter of a bug suggest how important it will be to the programmer who ends up fixing it. In practice, however, some programmers like spending most of their time fixing obscure crasher bugs, while other programmers perfer fixing "trivial" UI embarrassments. And in Malone, the Severity field isn't present on the page for reporting a bug anyway. Therefore it exists mainly for the assignee to indicate how important the bug is for them personally -- but hang on, the programmer already has a Priority field for that! So there's no point in having Severity too.
In Bugzilla, the presence of the Severity field also causes fun but useless and time-wasting arguments between the commenters on a bug about how important a bug actually is, especially since the reporter of a bug is likely to overestimate its severity (e.g. if a quirk of their system leads them to encounter the bug much more often than everyone else). These arguments occur far less often for the Priority field, because that is understood as the programmer's business and no-one else's.
Severity + Priority as separate fields occurs in:
* Malone
* Bugzilla.
A single field is used in:
* FogBuz (Priority)
* Jira (Priority)
* Plone Collector (Importance). |
Malone currently includes a Severity field. In Bugzilla, this field lets the reporter of a bug suggest how important it will be to the programmer who ends up fixing it. In practice, however, some programmers like spending most of their time fixing obscure crasher bugs, while other programmers prefer fixing "trivial" UI embarrassments. And in Malone, the Severity field isn't present on the page for reporting a bug anyway. Therefore it exists mainly for the assignee to indicate how important the bug is for them personally -- but the programmer already has a Priority field for that! So there's no point in having Severity too.
In Bugzilla, the presence of the Severity field also causes fun but useless and time-wasting arguments between the commenters on a bug about how important a bug actually is, especially since the reporter of a bug is likely to overestimate its severity (e.g. if a quirk of their system leads them to encounter the bug much more often than everyone else). These arguments occur far less often for the Priority field, because that is understood as the programmer's business and no-one else's.
Severity + Priority as separate fields occurs in:
* Malone
* Bugzilla.
A single field is used in:
* Debbugs (Severity)
* FogBuz (Priority)
* Jira (Priority)
* Plone Collector (Importance). |
|
| 2005-12-01 16:38:47 |
Matthew Paul Thomas |
summary |
Malone currently includes a Severity field |
|
|
| 2005-12-09 14:48:05 |
Brad Bollenbach |
malone: status |
Accepted |
NeedInfo |
|
| 2006-01-10 02:22:06 |
Matthew Paul Thomas |
description |
Malone currently includes a Severity field. In Bugzilla, this field lets the reporter of a bug suggest how important it will be to the programmer who ends up fixing it. In practice, however, some programmers like spending most of their time fixing obscure crasher bugs, while other programmers prefer fixing "trivial" UI embarrassments. And in Malone, the Severity field isn't present on the page for reporting a bug anyway. Therefore it exists mainly for the assignee to indicate how important the bug is for them personally -- but the programmer already has a Priority field for that! So there's no point in having Severity too.
In Bugzilla, the presence of the Severity field also causes fun but useless and time-wasting arguments between the commenters on a bug about how important a bug actually is, especially since the reporter of a bug is likely to overestimate its severity (e.g. if a quirk of their system leads them to encounter the bug much more often than everyone else). These arguments occur far less often for the Priority field, because that is understood as the programmer's business and no-one else's.
Severity + Priority as separate fields occurs in:
* Malone
* Bugzilla.
A single field is used in:
* Debbugs (Severity)
* FogBuz (Priority)
* Jira (Priority)
* Plone Collector (Importance). |
Malone's Severity and Priority fields have social and practical problems. "Severity" implies something that can objectively be set by bug reporters, but reporters and subscribers overestimate it for a variety of psychological reasons. And Priority is not useful as long as Severity exists, because some people treat Priority as a subdivision of Severity (major P4 > normal P1) and others don't.
To solve these problems, and to make Malone simpler, Severity and Priority should be merged into a single Importance field (like Plone Collector uses). This field could have the values "-" (unprioritized), "Trivial", "Minor", "Medium", "Major", "Critical", and "Urgent".
This is part of <https://wiki.launchpad.canonical.com/SimplifyingMalone>. |
|
| 2006-01-10 02:22:06 |
Matthew Paul Thomas |
title |
"Severity" field is more counterproductive than useful |
Merge Severity and Priority into Importance |
|
| 2006-01-10 02:22:27 |
Matthew Paul Thomas |
malone: status |
Needs Info |
Confirmed |
|
| 2006-03-31 20:18:50 |
Matthew Paul Thomas |
malone: status |
Confirmed |
In Progress |
|
| 2006-03-31 20:18:50 |
Matthew Paul Thomas |
malone: assignee |
bradb |
mpt |
|
| 2006-03-31 20:18:50 |
Matthew Paul Thomas |
malone: statusexplanation |
|
|
|
| 2006-03-31 20:19:48 |
Brad Bollenbach |
malone: priority |
Medium |
High |
|
| 2006-05-23 10:56:19 |
Matthew Paul Thomas |
malone: status |
In Progress |
Fix Committed |
|
| 2006-06-07 23:18:50 |
Brad Bollenbach |
malone: status |
Fix Committed |
Fix Released |
|
