From: Miguel A. Figueroa-V. <mi...@ie...> - 2009-03-16 23:30:52
|
On Mon, Mar 16, 2009 at 1:37 PM, Wheeler, Frederick W (GE, Research) wrote: >> > For each ticket component I suggest we have an "other" or >> "dontknow" or "unknown" category. You can never anticipate >> all possible situations or uses for a tracker, and I always >> find it very frustrating when I'm confronted with a >> multiple-choice form that does not give me an appropriate selection. >> > >> > Just my 2 cents. Miguel, this is your call. >> > >> > Fred >> > >> >> Hello Fred, >> >> You mean "*For each* ticket component" or just to have one >> component for "other" issues? >> >> If it is the latter, then that is the idea of the default "None" >> component, but I was thinking of changing it to "unknown" or >> "dontknow" for the same reasons you present. Is there a >> reason to have both "None" and "unknown"? >> >> --Miguel > > I'll try to explain my point better. > > What I meant was that for the ticket Type field there should > be an "other" option and possibly also an "unknown" option. > A ticket might be a tidbit of additional documentation, might > be a copyright concern, or might be a suggestion like this > about the ticket system itself. None of these fit cleanly in > the existing options, and we could never come up with a > comprehensive set of options. Also, an originating submitter > may not clearly understand what kind of issue they are > raising, hence the "unknown" option. > > Similarly, I think the Priority field should have an "unknown" > option. A bug reporter might not know whether the reported > problem is serious or not. Selecting "unknown" makes that > clear, then one of the maintainers can set that field appropriately. > > I suggest that all fields have some option that makes sense > if no other option seems to fit, and and option to select if you > just don't know what to select. > > I see that Milestone and Version can be left blank, so that sort > of addresses the issue. Still, adding an "unknown" option for > them helps the submitter who does not know what those things > mean, and does not know whether the ticket will be accepted > without selecting them. > > Again, if this makes sense and you think it is a good idea, great. > If not, don't worry about it. Thanks for setting up the tracker. > If you want to discuss this more, we could use the tracker! > > Fred Ok, the misunderstanding was due to the fact that one of the categories that the ticket has is "component". I guess it was all in the level of indirection of the word component :) I added a "Don't Know" and changed "None" to "Other" for the component field. Added "dont_know" to priority and type fields. Changed the "VXL To Be Determined" milestone to "Don't Know". For the version field I didn't add the don't know or other, because the user should know the version of the product that is failing. I would like to encourage the users to submit an appropriate ticket. Also, there is a field I would like to have for platform (i.e., Windows, Mac, Linux, etc.) and compiler, but for that I need access to the trac.ini. Maybe if I open a support ticket I can get sourceforge people to add it. However, I need to refine it before submitting. Thoughts on whether it is worth the trouble? --Miguel |