Re: [Wtr-general] Bad Bug Reports

2006-03-17 Thread Zeljko Filipin
I think we should put something like this at some visited place: We would like to help you, but we are very busy. We answer e-mails inour free time, so please help us help you. We will first answere-mails that follow this simple rules. From The Basics of Bug Tracking (FogBugz Documentation):

Re: [Wtr-general] Bad Bug Reports

2006-03-17 Thread Hugh Sasse
On Fri, 17 Mar 2006, Zeljko Filipin wrote: I think we should put something like this at some visited place: People who don't bother to provide full information are probably too busy to read such a document. However: We would like to help you, but we are very busy. We answer e-mails inour

Re: [Wtr-general] Bad Bug Reports

2006-03-17 Thread Zeljko Filipin
http://www.fogcreek.com/FogBugz/docs/40/Articles/TheBasicsofBugTracking.html From The Basics of Bug Tracking (FogBugz Documentation): (presumably that isn't on line?It would be useful to know...) ___ Wtr-general mailing list Wtr-general@rubyforge.org

Re: [Wtr-general] Bad Bug Reports

2006-03-17 Thread Hugh Sasse
On Fri, 17 Mar 2006, Zeljko Filipin wrote: http://www.fogcreek.com/FogBugz/docs/40/Articles/TheBasicsofBugTracking.html Thanks. That is a good article. I've just created an account for the FAQ. Lots of the entries have {anchor:...} markup (in the edit view). How does one reference these?

Re: [Wtr-general] Bad Bug Reports

2006-03-17 Thread Hugh Sasse
On Fri, 17 Mar 2006, Zeljko Filipin wrote: the new one http://jira.openqa.org/browse/WTR the old one http://rubyforge.org/tracker/?group_id=104 I've added these to my new Watir page, in the hope that this will nudge google et al to look in the right place. Patches, corrections etc