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

Summary	"capture" compatibility issues - make it easy for submitters
Queue	Horde Groupware
Queue Version	1.2.8
Type	Enhancement
State	Rejected
Priority	1. Low
Owners
Requester	tech (at) heiwi (dot) co (dot) nz
Created	12/14/2010 (5316 days ago)
Due	12/16/2010 (5314 days ago)
Updated	12/14/2010 (5316 days ago)
Assigned
Resolved	12/14/2010 (5316 days ago)
Milestone
Patch	No

12/14/2010 11:29:41 PM	Michael Rubinsky	Comment #2 State ⇒ Rejected Priority ⇒ 1. Low	Reply to this comment
[Show Quoted Text - 21 lines][Hide Quoted Text] 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.

12/14/2010 11:10:57 PM	tech (at) heiwi (dot) co (dot) nz	Comment #1 State ⇒ New Priority ⇒ 2. Medium Type ⇒ Enhancement Summary ⇒ "capture" compatibility issues - make it easy for submitters Due ⇒ 12/16/2010 Queue ⇒ Horde Groupware Milestone ⇒ Patch ⇒ No	Reply to this 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?