View Issue Details

IDProjectCategoryView StatusLast Update
0004102mantisbtbugtrackerpublic2011-10-04 03:42
Reportervboctor Assigned Tovboctor  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version0.19.0a1 
Fixed in Version1.1.0a1 
Summary0004102: 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:

  • Add the possibility to configure the default category, this way there can be an unknown or unfiled category.
  • Add a blank category at the top that is selected by defaulted, and make category a mandatory field, therefore if the user forgets to set it, an error message will be prompted (same like summary / description now).
TagsNo tags attached.

Relationships

related to 0008582 assigneddregad Default Category for Project / Global default Category 
has duplicate 0004933 closedthraxisp Be able to set a category to be the 'default' category and/or default it to 'empty' to force user to make selection 

Activities

gtomlin

gtomlin

2004-11-24 11:06

reporter   ~0008421

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,
like "- please specify -" or "- unknown -". But that (as well as actually configuring a default category) still could result in numerous problems defaulted to a garbage category. But at least it gets us from wrong information to missing information.

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.

Matt_wc

Matt_wc

2004-11-24 22:24

reporter   ~0008424

Personally, I like the second solution as well. This way the issues will have a more accurate catagory applied straight away.

vboctor

vboctor

2006-04-22 02:20

manager   ~0012679

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.