Bug 277857 – ascii text console bug report input via links, non-graphical browser input, limits on number of char input into which text input fields, no file attachments possible in console mode

• Status: RESOLVED TEST-REQUEST
• Product: Gentoo Infrastructure

[Description Werner M. Mayer 2009-07-14 19:37:54 UTC]

When I run into bugs, I am mostly in console mode and use console tools like 
  links to post bugs, just as I am doing so now. 

  Trying to switch between pc with gentoo problem and graphical input on another
  pc or laptop with the need to transfer bug reporting data between the two is
  much to time consuming and a large effort to cope with really.

  Each field of text (Summary, description, reproducibility, actual results,
  expected results, additional Information) allows input of chars, but I don't 
  know how much chars in each field, so this is what this bug report is aiming 
  at, getting to know which input field allows how many chars.

  Why is this important?

  Whenever I post a bug in console mode, I seem to exceed the maximum field
  lengths available, and I also get an error to correct my input when I submit, 
  but then again I don't get feedback as to which input field needs input 
  shortening, just an error saying my input exceeds 16kb.

  I would therefore kindly like to ask you to add the missing info to the
  input field descriptions so that the bug reporter reporting bugs via ascii
  console via text browsing tools like lynx or links has to possibility to
  put just enough info into the appropriate input fields.

  Another reason for this being important is that appending files is at least
  very complicated to very difficult to impossible in console text mode input.

  I've already lost major bug reports I refused to retype due to the effort it
  implies. Just now I've lost another one by paging back and forth and hitting
  a wrong key. It is quite frustrating. Maybe I'll report on the new bug again
  tonight, but not again to the same detailed extent as previously.

  Now what I'd like to have is something like I have on ebay, where I get the 
  info how many chars are left, but without the drawback on ebay that my text
  gets cut off.
  So when I hit the submit button and get an error message, and hitting the 
  back-button, the descriptive info text in my bug form shows me exactly how 
  many chars I have left over or with a minus, how many chars I have too much.

Reproducible: Always

Steps to Reproduce:
  1.at every bug report



Actual Results:  
  Error message saying my bug report is too long. 

Expected Results:  
  What I want:
  Error message telling me at which input field I have put how many of the too
  much chars, e.g. 200 chars too much in field additional information and how
  many input chars are still free at the other input fields.
  Of course I know that this kind of info isn't nearly as easy to get as on a
  graphical form.

see expected results.

To Severity: It's a bug that should be fixed.
It may also be a feature the console bug reporting system lacks.
As this is my main way of reporting bugs, for me, it's a bug.

[Comment 1 Christian Ruppert (idl0r) 2010-08-08 09:23:43 UTC]

It wouldn't solve the main problem but you should try www-client/pybugz anyway.

[Comment 2 Christian Ruppert (idl0r) 2011-03-07 17:28:24 UTC]

Now that we're running bugzilla-4.x, is it still an issue?