On Tuesday 21 March 2006 15:20, Chad Smith wrote: > I assume this macro would automatically record the OOo version, the > system's OS, and stuff like that, right? (I didn't see that in the > orginial suggestion - just wondering if that was the thinking.)
I was thinking only of the web interface for reporting bugs. But obviously the principle could be applied anywhere where a bug description is being collected. Any automatic collection of information is welcomed, provided it is reliable. Andy. > > On 3/21/06, Henrik Sundberg <[EMAIL PROTECTED]> wrote: > > 2006/3/21, Andy Pepperdine <[EMAIL PROTECTED]>: > > > On Tuesday 21 March 2006 13:58, Ross Johnson wrote: > > > > One thing is for sure though - providing a good problem description, > > > > clear reproducible steps and a sample test case will usually get your > > > > report confirmed by the QA people more quickly, and that means a > > > > developer will see it sooner. Beyond that I can't say. > > > > I really like this idea. Hope it's doable. > > > > > The difficulty is getting a good problem description. In my experience, > > > > most > > > > > users of any product need a special mindset to give such a description, > > > > and > > > > > if you ask two users to describe the same bug, you'll get two very > > > > different > > > > > answers. In our case, we are expecting them to know how to describe > > > > something > > > > > remotely. > > > > > > If I was talking to someone about an issue, I would try to establish: > > > 1. What did you do to create the error? > > > 2. What happened when you did that? > > > 3. What did you expect to happen? > > > This last one is important because it can often cause the user to > > > > question > > > > > their own assumptions and realise the problem for themselves. Not > > > > always, > > > > > certainly, but it may reduce the noise. > > > > I think the last question is very important for other reasons as well. > > It makes it much easier for the developer to understand what the user > > focused on and it is very useful for regression tests. > > > > > So I wonder whether instead of a single box for a description, we > > > should divide it into three questions as above. Or perhaps just prime > > > the box > > > > with > > > > > three questions in it already. I've never seen this tried, so I have no > > > > idea > > > > > how it would be received. > > > > I would be very happy with such a system. Both as a user and a > > developer (not OOo developer). > > > > > One trivial thing though would be to reverse the version list so the > > > > most > > > > > recent are at the top (at least for Writer you've got to scroll down to > > > > the > > > > > bottom to find the most recent version). > > > > Don't understand what you talk about here. > > > > /$ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > -- > - Chad Smith > http://www.gimpshop.net/ > http://www.whatisopenoffice.org/ > Because everyone loves free software! > http://www.chadwsmith.com/ > Because, admit it, you've got nothing better to do right now... -- Andy Pepperdine On this mailing list help is provided by volunteers. Please subscribe to the mailing list to see all the replies to a query, and reply only to the mailing list at [EMAIL PROTECTED] For FAQ, userguide, see: http://documentation.openoffice.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
