View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001872 | mantisbt | bugtracker | public | 2002-04-22 10:06 | 2004-08-29 02:14 |
Reporter | magico | Assigned To | vboctor | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | won't fix | ||
Product Version | 0.17.1 | ||||
Summary | 0001872: Super simple report / simple report / advanced report | ||||
Description | Even the simple report, provides some 'extra' things, not needed by normal users (not us programmers). Why this? Simple, many users don't like to report bugs (especially to write them) and if we ask them to fill a form with some fields they refuse to do it. Off course the problem is always our (because I'll have to listen them and fill the form myself). So, if we have only a description field, they can write what they want and then when reading the bugs, we'll assign the correct category and other information. | ||||
Tags | No tags attached. | ||||
related to | 0004227 | acknowledged | Roadmap 1.0 - Templates |
customizable fields and being able to create your own reports is something I think would really benefit mantis. I hope we can see this atleast one day in the near future. |
|
Full ACK. Lowering the barriers to submitting bug reports is always a benefit. |
|
There is the need to strike the balance between stooping to laziness and requiring enough information to be able to fix the issue. THis sort of thing is on the long term roadmap. |
|
Please make the report forms table driven. For example the following table could be used to create your advanced report form: Field Action Access Default A super simple form might look like: Summary, Required, >=reporter Obviously this is a first cut that may not have the features you really need, but you can see that such a table would allow users to easily customize bug reporting screens from kitchen sink - to description only. |
|
Summary and description are now the only two required fields. Th drop downs are automatically set on some valid entry. |
|
I'll see about the table driven selectable inputs. Probably roll something in 0.18.0 |
|
This will be achieved when template support is implemented. |
|