TEXT   19

filing txt

Guest on 22nd July 2022 01:51:19 AM

  1. Filing a Bug
  2. ************
  3.  
  4.  
  5. Reporting a New Bug
  6. ===================
  7.  
  8. Years of bug writing experience has been distilled for your reading
  9. pleasure into the Bug Writing Guidelines. While some of the advice is
  10. Mozilla-specific, the basic principles of reporting Reproducible,
  11. Specific bugs and isolating the Product you are using, the Version of
  12. the Product, the Component which failed, the Hardware Platform, and
  13. Operating System you were using at the time of the failure go a long
  14. way toward ensuring accurate, responsible fixes for the bug that bit
  15. you.
  16.  
  17. Note: If you want to file a test bug to see how Bugzilla works, you
  18.   can do it on one of our test installations on Landfill. Please don't
  19.   do it on anyone's production Bugzilla installation.
  20.  
  21. The procedure for filing a bug is as follows:
  22.  
  23. 1. Click the New link available in the header or footer of pages,
  24.    or the File a Bug link on the home page.
  25.  
  26. 2. First, you have to select the product in which you found a bug.
  27.  
  28. 3. You now see a form where you can specify the component (part of
  29.    the product which is affected by the bug you discovered; if you
  30.    have no idea, just select General if such a component exists), the
  31.    version of the program you were using, the operating system and
  32.    platform your program is running on and the severity of the bug (if
  33.    the bug you found crashes the program, it's probably a major or a
  34.    critical bug; if it's a typo somewhere, that's something pretty
  35.    minor; if it's something you would like to see implemented, then
  36.    that's an enhancement).
  37.  
  38. 4. You also need to provide a short but descriptive summary of the
  39.    bug you found. "My program is crashing all the time" is a very poor
  40.    summary and doesn't help developers at all. Try something more
  41.    meaningful or your bug will probably be ignored due to a lack of
  42.    precision. In the Description, give a detailed list of steps to
  43.    reproduce the problem you encountered. Try to limit these steps to
  44.    a minimum set required to reproduce the problem. This will make the
  45.    life of developers easier, and the probability that they consider
  46.    your bug in a reasonable timeframe will be much higher.
  47.  
  48.    Note: Try to make sure that everything in the Summary is also in
  49.      the Description. Summaries are often updated and this will ensure
  50.      your original information is easily accessible.
  51.  
  52. 5. As you file the bug, you can also attach a document (testcase,
  53.    patch, or screenshot of the problem).
  54.  
  55. 6. Depending on the Bugzilla installation you are using and the
  56.    product in which you are filing the bug, you can also request
  57.    developers to consider your bug in different ways (such as
  58.    requesting review for the patch you just attached, requesting your
  59.    bug to block the next release of the product, and many other
  60.    product-specific requests).
  61.  
  62. 7. Now is a good time to read your bug report again. Remove all
  63.    misspellings; otherwise, your bug may not be found by developers
  64.    running queries for some specific words, and so your bug would not
  65.    get any attention. Also make sure you didn't forget any important
  66.    information developers should know in order to reproduce the
  67.    problem, and make sure your description of the problem is explicit
  68.    and clear enough. When you think your bug report is ready to go,
  69.    the last step is to click the Submit Bug button to add your report
  70.    into the database.
  71.  
  72.  
  73. Clone an Existing Bug
  74. =====================
  75.  
  76. Bugzilla allows you to "clone" an existing bug. The newly created bug
  77. will inherit most settings from the old bug. This allows you to track
  78. similar concerns that require different handling in a new bug. To use
  79. this, go to the bug that you want to clone, then click the Clone This
  80. Bug link on the bug page. This will take you to the Enter Bug page
  81. that is filled with the values that the old bug has. You can then
  82. change the values and/or text if needed.
  83.  
  84. ======================================================================
  85.  
  86. This documentation undoubtedly has bugs; if you find some, please file
  87. them here.

Raw Paste


Login or Register to edit or fork this paste. It's free.