From: lpsolit%gmail.com <> Date: Fri, 8 Dec 2006 02:23:21 +0000 (+0000) Subject: Bug 355302: Documentation for the "clone bug" feature - Patch by victory(_RSZ_) ... X-Git-Tag: bugzilla-2.20.4~4 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=cf2cedb2a430e40ce603179c0ffb0cfe19b015e2;p=thirdparty%2Fbugzilla.git Bug 355302: Documentation for the "clone bug" feature - Patch by victory(_RSZ_) r=vladd --- diff --git a/docs/xml/using.xml b/docs/xml/using.xml index c871fbd6dd..30afe40132 100644 --- a/docs/xml/using.xml +++ b/docs/xml/using.xml @@ -579,91 +579,94 @@
Filing Bugs - Years of bug writing experience has been distilled for your - reading pleasure into the - - Bug Writing Guidelines. - While some of the advice is Mozilla-specific, the basic principles of - reporting Reproducible, Specific bugs, isolating the Product you are - using, the Version of the Product, the Component which failed, the - Hardware Platform, and Operating System you were using at the time of - the failure go a long way toward ensuring accurate, responsible fixes - for the bug that bit you. - - The procedure for filing a bug is as follows: +
+ Reporting a New Bug + + Years of bug writing experience has been distilled for your + reading pleasure into the + + Bug Writing Guidelines. + While some of the advice is Mozilla-specific, the basic principles of + reporting Reproducible, Specific bugs, isolating the Product you are + using, the Version of the Product, the Component which failed, the + Hardware Platform, and Operating System you were using at the time of + the failure go a long way toward ensuring accurate, responsible fixes + for the bug that bit you. + + The procedure for filing a bug is as follows: + + + + + Click the New link available in the footer + of pages, or the Enter a new bug report link + displayed on the home page of the Bugzilla installation. + - - - - Click the New link available in the footer - of pages, or the Enter a new bug report link - displayed on the home page of the Bugzilla installation. - + + + If you want to file a test bug to see how Bugzilla works, + you can do it on one of our test installations on + Landfill. + + + - + - If you want to file a test bug to see how Bugzilla works, - you can do it on one of our test installations on - Landfill. + You first have to select the product in which you found a bug. - - + - - - You first have to select the product in which you found a bug. - - + + + You now see a form where you can specify the component (part of + the product which is affected by the bug you discovered; if you have + no idea, just select General if such a component exists), + the version of the program you were using, the Operarting System and + platform your program is running on and the severity of the bug (if the + bug you found crashes the program, it's probably a major or a critical + bug; if it's a typo somewhere, that's something pretty minor; if it's + something you would like to see implemented, then that's an enhancement). + + - - - You now see a form where you can specify the component (part of - the product which is affected by the bug you discovered; if you have - no idea, just select General if such a component exists), - the version of the program you were using, the Operarting System and - platform your program is running on and the severity of the bug (if the - bug you found crashes the program, it's probably a major or a critical - bug; if it's a typo somewhere, that's something pretty minor; if it's - something you would like to see implemented, then that's an enhancement). - - + + + You now have to give a short but descriptive summary of the bug you found. + My program is crashing all the time is a very poor summary + and doesn't help developers at all. Try something more meaningful or + your bug will probably be ignored due to a lack of precision. + The next step is to give a very detailed list of steps to reproduce + the problem you encountered. Try to limit these steps to a minimum set + required to reproduce the problem. This will make the life of + developers easier, and the probability that they consider your bug in + a reasonable timeframe will be much higher. + - - - You now have to give a short but descriptive summary of the bug you found. - My program is crashing all the time is a very poor summary - and doesn't help developers at all. Try something more meaningful or - your bug will probably be ignored due to a lack of precision. - The next step is to give a very detailed list of steps to reproduce - the problem you encountered. Try to limit these steps to a minimum set - required to reproduce the problem. This will make the life of - developers easier, and the probability that they consider your bug in - a reasonable timeframe will be much higher. - + + + Try to make sure that everything in the summary is also in the first + comment. Summaries are often updated and this will ensure your original + information is easily accessible. + + + - + - Try to make sure that everything in the summary is also in the first - comment. Summaries are often updated and this will ensure your original - information is easily accessible. + Now is a good time to read your bug report again. Remove all misspellings, + otherwise your bug may not be found by developers running queries for some + specific words, and so your bug would not get any attention. + Also make sure you didn't forget any important information developers + should know in order to reproduce the problem, and make sure your + description of the problem is explicit and clear enough. + When you think your bug report is ready to go, the last step is to + click the Commit button to add your report into the database. - - - - - - Now is a good time to read your bug report again. Remove all misspellings, - otherwise your bug may not be found by developers running queries for some - specific words, and so your bug would not get any attention. - Also make sure you didn't forget any important information developers - should know in order to reproduce the problem, and make sure your - description of the problem is explicit and clear enough. - When you think your bug report is ready to go, the last step is to - click the Commit button to add your report into the database. - - - + + You do not need to put "any" or similar strings in the URL field. @@ -676,6 +679,22 @@ the bug it was duped to. Feel free to CC the person who duped it if they are not already CCed. +
+ +
+ Clone an Existing Bug + + + Starting with version 2.20, Bugzilla has a feature that allows you + to clone an existing bug. The newly created bug will inherit + most settings from the old bug. This allows you to track more + easily similar concerns in a new bug. To use this, go to the bug + that you want to clone, then click the Clone This Bug + link on the bug page. This will take you to the Enter Bug + page that is filled with the values that the old bug has. + You can change those values and/or texts if needed. + +
@@ -804,7 +823,7 @@
Hints and Tips - + This section distills some Bugzilla tips and best practices that have been developed. @@ -828,7 +847,7 @@ Most other sorts of URL - + A corollary here is that if you type a bug number in a comment, you should put the word "bug" before it, so it gets autolinkified for the convenience of others. @@ -865,14 +884,14 @@ and add a comment saying "Adding self to CC", then that person gets a pointless piece of mail they would otherwise have avoided. - + Don't use sigs in comments. Signing your name ("Bill") is acceptable, if you do it out of habit, but full mail/news-style four line ASCII art creations are not. - +
- +
Dependency Tree