Stop including your personal opinions as to what happed and just what did, where it did and at what time and you'll be fine.
If you need to add more than that then use the form on the main site.
[ QUOTE ]
Stop including your personal opinions as to what happed and just what did, where it did and at what time and you'll be fine.
If you need to add more than that then use the form on the main site.
[/ QUOTE ]
Yes. As it happens, I know quite well what should be in a bug report. 
But believe it or not it could be quite a lot, because you'd rather tell EXACTLY what you did and how.
Which contact/mission it was|? (yes, it's supposed to be in the auto-generated part but wouldn't be in my case b/c of the nature of the bug.) Were you getting the same result every time you tried and what exactly, step-by-step, you did? (You know, probably, that most insidious type of bug is one where you're supposed to do A or B in either order, but in fact doing A then B produces different results from B then A?)
Any other facts you feel you should add? (Again, no opinion on WHY bug happens is very good, but if the bug happens, say, only when you use wireless mouse and not touchpad might be important.)
And that wrongly enforced 50-character limit in the header is a bug in itself.
If you can't include all that information in 510 characters, you need to write more concisely.
The devs are just as vunerable to the lethal Wall-of-Text +10 as anyone. Throw to many words at them and they are likely to miss the important ones.
I really should do something about this signature.
After 10000th "not reproduced"-"reopened"-"Ah, it was because you pressed ENTER, not clicked the OK button!" "Fixed for good" "reopened - TAB to focus on the button then, then SPACE still doesn't work right" bug you are vulnerable to obsessive-compulsive behaviour... 
Well, after a night's sleep it seems that the main problem with that particular report was that both mission and contact names were extremelly long-winded, and there was absolutely no way to avoid those. If it was something shorter, it'd probably would be much easier to fit it all in 500 chartacters without sounding TOO concise. (affects readability 2,BTW.)
I still think that 1000 characters would be better, but well...
Why are we limited to just 510 characters in /bug report body and 50 in the header? Furthermore, the dialog allows more than 50 characters to be typed into the header field, so you may think you're OK, but then your header is cut mid-word.
And 10 characters with no paragraphs is too little. (I bet that there's some QA guy right now trying to make sense of my bug report, because I had to shoehorn lots of related facts inrto that stupid limit.)
Ok, I understand that there ought to be a limit of some kind for the whole host of reasons but won't allowing users to add more info if they can add to theirt usefulness?