It would be nice if bugzilla would enforce a limit on the number of lines (or just the number of characters) for the comments field (along with instructions to attach the "comment" as a text file instead). The check should probably be made by the backend, not the frontend, in order to allow reporters to hit the "Back" button in their browser and cut-n-paste their comment to a file instead. This would make it impossible to clutter a bug with long compilation output, kernel .config files etc. Stuff which really belongs in the attachment section. Needless to say, the limit should be set reasonably high in order for smaller compilation outputs to be posted as comments.
Not only comment field should be limited, summary needs limit as well: http://bugs.gentoo.org/show_activity.cgi?id=124029
This is definitely something upstream if it's going to be included in the back-end of bugzilla. I am no bugzilla programmer by any stretch of the imagination.
Reopening as this is something being worked on
Created attachment 87022 [details] Sample JS I understand that you are looking into actually placing a hard restriction via bugzilla's configuration, but I produced some simple javascript which implements what I was thinking of anyway. Either solution is good by me.
Thanks to the work of Jakub and Daniel, we have instituted an 8000 character limit on the comment field. This will go live when i push bugstest out to bugs, just waiting on confirmation of the backend DB stuffs first.
(In reply to comment #5) > Thanks to the work of Jakub and Daniel, we have instituted an 8000 character > limit on the comment field. 8000 characters? Why so high?
(In reply to comment #6) > 8000 characters? Why so high? # emerge --info | wc -c 3332 And - I'm not using even remotely as many use flags as some of the people do. We should not nag them more than necessary to prevent posting huge crap like kernel .config or complete config.log
(In reply to comment #7) > # emerge --info | wc -c > 3332 Hmm, I was actually hoping this would enforce people to attach their 'emerge --info' output instead of pasting it as a comment. Having a bug report with just three or four 'emerge --info' posts gets quite huge and is not easily parsed.
(In reply to comment #8) > Hmm, I was actually hoping this would enforce people to attach their 'emerge > --info' output instead of pasting it as a comment. Having a bug report with > just three or four 'emerge --info' posts gets quite huge and is not easily > parsed. Not a good idea at least until mime type autodetection either works correctly or is removed from bugzilla and it defaults to plaintext. I certainly don't want to be forced to edit the attachment mime type to be able to see plain emerge --info output. :)
