Tickets :: Comment on [#9450] "capture" compatibility issues

* Your Email Address
* Spam protection	Enter the letters below: . ..__ .__ .. . \ /[__)[ __ \|\| \| \/ \| \[_./\__\|\|/\\|
Comment	>> Hello, >> >> Just a suggestion. >> Not wanting to add complexity (which should be reduced) to the bug >> report system. >> But ... >> >> 1) To make it easier to reports bugs; >> Use as little mandatory questions, and choice procedures as possible. >> Some kind hearted folk who are taking the time to talk to you, may >> get fed up with ancilliary comms and leave - then you learn Nothing >> new from them. >> >> 2) No harm in capturing additional information - if the submitter is >> capable, knowledgeable enough or willing to provide it. >> Useful information to help understand the "context" of a problem >> might include ; >> - is your Horde program being used within a site management system >> such as cPanel or Fantastico? >> - is horde on your own in-house network, or at your isp. >> - feel free to tell us more about how you are accessing Horde online? > > While these are good communication practices, this is a bug > tracking system for Horde code. Information such as this may be > useful, but not in the context of a bug/issue tracker. i.e., if your > horde install is run by your isp, then you shouldn't be reporting a > bug to horde. >
Attachment
Watch this ticket