While writing a new bug, there is no way to attach new attachments that I could find. I looked everywhere in the form, and could not find it. If it's there, make it not invisible, and if it is not there, put it there.
Of course there *is* a way... File a bug, and *then* attach something - using the "Create a New Attachment" feature, just above the comment field. Everyone does that, in thousands of bugs.
(In reply to comment #1) > Of course there *is* a way... File a bug, and *then* attach something - using > the "Create a New Attachment" feature, just above the comment field. Everyone > does that, in thousands of bugs. It should be specified in the system that this is the method to add attachments, so one does not input incorrect text into the initial text in the first place.
It should be specified in the system that clicking on Create a New Attachment link makes it possible to create an attachment? Looks, I've been really patient, but this starts to be too much really... http://www.gentoo.org/doc/en/bugzilla-howto.xml#doc_chap6 Review the above howto if you have any additional questions.
I also think the complaint of bugzilla is fuzzy: when message is too long, it complains about, and asks to create an attachment. But, it does not says HOW to do it ! Low skilled and recent users of bugzilla may not notice that there is a "create attach" option after bug creation; thus, it seems quiet legitimate to me to worry about attachment DURING bug creation ! Red message says to "do" it, not that we have to wait first, shot creation, and then *later* we will be "allowed" to attach it ... this is clearly counter intuitive to me ! If you are not to add attcj creation feature at bug creation (and there could be technical reasons for this), please AT LEAST change the RED MESSAGE, into something like: * Please your message is too long; make it shorter, keep logs and long listings aside, and put them as attachment after bug creation is compleet * The actual state of art is counter intuitive; I ask at least for some changes in messages shown, messages that would make things clear. Proof they are not clear: Brad and myself did not understood what to do. An explicit RED MESSAGE would avoid head scraching. But, it would even be a better idea to make an allusion to this in the main page, so that reporters do not start by entering long message, and then get stuck. Especially reporters with low experience may get crazy when understanding they will have to delete everything, and use an other method to report the bug. This kind of problem often leaded me in closing browser, and not report the problem at all. When too angry, I also skipped the newt bug I encontoured. Thanks.
