Comment 10 for bug 78911

During implementation, I'd like to request that the available length either be long enough to include all of 1) A fair description of the nature of the issue (Usually oughtn't be more than two or three paragraphs), 2) relevant notes from exterior sources (maybe up to three paragraphs), 3) A full test case descrption, including observed and expected results, and 4) A paragraph of additional notes that may be important to testers, or other subscribers waiting for input results.

I can easily imagine all of the above being more than 1000 characters, but would find implementation of some of the more complex StableReleaseUpdates more difficult to process without that information. Further, there may be lengthy comments that are useful in discussion of whether something is a bug, or related items that are of direct interest to bug subscribers, yet nonetheless larger than such a small numerical limit.

On the other hand, huge pastes of log files, debug output, etc. is essentially useless, as it makes it harder to extract than an attachment and detracts from understanding of the bug. Might it be possible to apply some heuristics to try to differentiate prose from log files? Further, if imposing a limit on bug descriptions, it may be useful to apply the same limit to bug comments, to discourage posting of logs as comments in an attempt to work around the description size limit (this may be more critical, as the description may at least be edited to a reasonable size).