Changes between Version 5 and Version 6 of reportbugs

Timestamp:

29/06/10 13:04:10 (3 years ago)

Author:

matthijs

Comment:

Add note to search for duplicates first

reportbugs

@@ -8 +8 @@
  * Leave your email address in the reporter field. If we can't reproduce the problem and we can't contact you, we can't fix the bug! As an added bonus, you'll get notified whenever the ticket changes status.
  * Use a concise, but complete summary. "Fonera problem" is a useless summary, "Music plugin problem" is not quite good, "Occasional reboots when using the music plugin for a few hours" is a good summary.
+ * Check if your bug or enhancement request has not been reported before. The normal "search" field of trac isn't well suited for this (you can't filter out closed reports), so you're better off doing a custom query (click "View Ticket" and then "Custom Query"). For a shortcut, [http://trac.fonosfera.org/fon-ng/query?status=accepted&status=assigned&status=confirmed&status=infoneeded&status=investigate&status=new&status=reopened&status=testnewer&summary=~&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&order=priority here is a query to search just the summary of open reports]. If you find your issue has been reported already, feel free to leave a comment so we can keep you updated and you can provide extra details if available.
  * Clearly describe the bug you found. Important questions are: "What were you doing when the bug occured?", "Can you reproduce the bug reliabley, and if so, what is the exact sequence of steps to take to trigger the bug?", "What hardware and what software version are you using?", "Is there a configuration value that can make the bug appear or go away?".
  * Provide as much relevant (!) details as possible. Are there configuration details that seem relevant to you? Does the output of the "{{{logread}}}" command contain related info?