View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004102 | mantisbt | bugtracker | public | 2004-07-15 06:32 | 2011-10-04 03:42 |
Reporter | vboctor | Assigned To | vboctor | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 0.19.0a1 | ||||
Fixed in Version | 1.1.0a1 | ||||
Summary | 0004102: Category field should be empty by default or default specified | ||||
Description | Given that the first category is selected by default, a lot of people just forget to set it to something else. Hence, the first category in the list ends up with a lot of issues that should have been under other categores. I believe there are two solutions:
| ||||
Tags | No tags attached. | ||||
I see this as an important issue from a quality control standpoint. Correct information is better than missing information, and missing information is better than wrong information. The first of the two solutions mentioned in the original issue report (Add the possibility to configure the default category) can be faked by adding a category that collates to the top of the list with a non-alphabetic character, The second solution (Add a blank category at the top that is selected by defaulted, and make category a mandatory field) is what I'd like to see. A change like that done for 0004091 plus checking like that done for summary should do the trick. The same logic should be applied to reproducibility and optionally to severity and priority. |
|
Personally, I like the second solution as well. This way the issues will have a more accurate catagory applied straight away. |
|
Added $g_default_bug_category to specify the default category. Since configuration can now be project specific, there can be a general default category or a default category per project. |
|