Closed
Bug 94548
Opened 23 years ago
Closed 16 years ago
If people paste a very long comment, suggest (or create) an attachment instead
Categories
(Bugzilla :: Creating/Changing Bugs, enhancement, P2)
Tracking
()
RESOLVED
DUPLICATE
of bug 130011
People
(Reporter: 2009-bugzilla, Unassigned)
References
()
Details
(Whiteboard: [content:comments])
As you can see at the mentioned url sstuart@applied-imagination.com added a 63k comment (a crash report). It is rather disturbing because - everyone got a 63k mail - bug-page load time increases for no reasonable reason - since the bug-page is full of unneccessary information you cannot find the end of the one or the begin of another submission. Maybe we should consider A) A maximum of lines, bytes, etc for a submission - if larger then it may only be used as attachement B) No maximum of lines, bytes, etc but Mozilla displays only the first 100 lines/4000 bytes, etc. and a -Read more- link
Comment 1•23 years ago
|
||
This is definitely a good idea.
Severity: normal → enhancement
Priority: -- → P1
Target Milestone: --- → Bugzilla 2.18
Comment 2•23 years ago
|
||
this is much needed
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Version: Bugzilla 2.13 → 2.10
Updated•23 years ago
|
Whiteboard: [content:comments]
Comment 4•23 years ago
|
||
*** This bug has been marked as a duplicate of 72184 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 5•23 years ago
|
||
This bug is in no way connected to the abilities of the backend database. It is about showing only part of the comment, or restricting the maximum length of a comment to a reasonable size. This bug doesn't cover attachements. Reopening.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 6•23 years ago
|
||
I'll concur with the reporter. Although they're closely related, these are actually two separate issues. Bug 72184 is dealing with making sure we don't send the database more than it can handle. This bug is about enforcing an arbitrary limit (which may be smaller than what the database can take) from the front end to avoid sending big emails to people.
Status: REOPENED → NEW
Comment 7•22 years ago
|
||
Theres a separate bug on attachments, and bug 72184 does make this a Param...
Comment 8•20 years ago
|
||
Enhancements which don't currently have patches on them which are targetted at 2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. Consideration will be taken for moving items back to 2.18 on a case-by-case basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Comment 9•20 years ago
|
||
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged enhancement that hasn't already landed is being pushed out. If this bug is otherwise ready to land, we'll handle it on a case-by-case basis, please set the blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Comment 10•19 years ago
|
||
Reassigning bugs that I'm not actively working on to the default component owner in order to try to make some sanity out of my personal buglist. This doesn't mean the bug isn't being dealt with, just that I'm not the one doing it. If you are dealing with this bug, please assign it to yourself.
Assignee: justdave → create-and-change
QA Contact: mattyt-bugzilla → default-qa
Updated•17 years ago
|
Priority: P1 → P2
Updated•17 years ago
|
Summary: Bugzilla accepts way-too-large submissions → If people paste a very long comment, suggest (or create) an attachment instead
Comment 12•16 years ago
|
||
Duplicate of bug 130011 ? (or the other way around ?)
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 23 years ago → 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•