View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006488 | mantisbt | customization | public | 2005-12-11 11:27 | 2006-05-07 03:51 |
Reporter | cdsmithus | Assigned To | vboctor | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.0.0rc3 | ||||
Fixed in Version | 1.1.0a1 | ||||
Summary | 0006488: Should be able to remove severity and reproducibility | ||||
Description | If I define g_severity_enum_string and g_reproducibility_enum_string to empty strings, I'd like to not see the corresponding fields in the web interface. I don't see any reason that these fields should be required. I'm trying to move casual testers over from BugZilla, and they are accustomed to ignoring fields when reporting bugs. The more pointless fields are on the bug report for them to fill in, then less likely they will get in the habit of filling out fields we care about. | ||||
Tags | No tags attached. | ||||
You could add priority to this list. In our situation, we always work on the highest severity issues first, and priority is thus redundant. |
|
Added $g_default_bug_reproducibility to default reproducibility. Fields like severity, priority, reproducibility, category are now all optional and can be removed from the form posting the issue. |
|