?? bugzilla-guide.txt
字號:
The Bugzilla Guide - 2.18.3 ReleaseThe Bugzilla Team 2005-07-09 This is the documentation for Bugzilla, a bug-tracking system from mozilla.org. Bugzilla is an enterprise-class piece of software that tracks millions of bugs and issues for hundreds of organizations around the world. The most current version of this document can always be found on the Bugzilla Documentation Page. _________________________________________________________________ Table of Contents 1. About This Guide 1.1. Copyright Information 1.2. Disclaimer 1.3. New Versions 1.4. Credits 1.5. Document Conventions 2. Installing Bugzilla 2.1. Installation 2.2. Configuration 2.3. Optional Additional Configuration 2.4. OS-Specific Installation Notes 2.5. UNIX (non-root) Installation Notes 3. Administering Bugzilla 3.1. Bugzilla Configuration 3.2. User Administration 3.3. Products 3.4. Components 3.5. Versions 3.6. Milestones 3.7. Flags 3.8. Voting 3.9. Quips 3.10. Groups and Group Security 3.11. Upgrading to New Releases 4. Bugzilla Security 4.1. Operating System 4.2. MySQL 4.3. Webserver 4.4. Bugzilla 5. Customising Bugzilla 5.1. Template Customization 5.2. Template Hooks 5.3. Customizing Who Can Change What 5.4. Modifying Your Running System 5.5. MySQL Bugzilla Database Introduction 5.6. Integrating Bugzilla with Third-Party Tools 6. Using Bugzilla 6.1. Introduction 6.2. Create a Bugzilla Account 6.3. Anatomy of a Bug 6.4. Life Cycle of a Bug 6.5. Searching for Bugs 6.6. Bug Lists 6.7. Filing Bugs 6.8. Patch Viewer 6.9. Hints and Tips 6.10. User Preferences 6.11. Reports and Charts 6.12. Flags A. The Bugzilla FAQ B. Troubleshooting B.1. General Advice B.2. The Apache webserver is not serving Bugzilla pages B.3. I installed a Perl module, but checksetup.pl claims it's not installed! B.4. Bundle::Bugzilla makes me upgrade to Perl 5.6.1 B.5. DBD::Sponge::db prepare failed B.6. cannot chdir(/var/spool/mqueue) B.7. Your vendor has not defined Fcntl macro O_NOINHERIT B.8. Everybody is constantly being forced to relogin B.9. Some users are constantly being forced to relogin B.10. index.cgi doesn't show up unless specified in the URL B.11. checksetup.pl reports "Client does not support authentication protocol requested by server..." C. Contrib C.1. Command-line Search Interface C.2. Command-line 'Send Unsent Bug-mail' tool D. Manual Installation of Perl Modules D.1. Instructions D.2. Download Locations D.3. Optional Modules E. GNU Free Documentation License 0. Preamble 1. Applicability and Definition 2. Verbatim Copying 3. Copying in Quantity 4. Modifications 5. Combining Documents 6. Collections of Documents 7. Aggregation with Independent Works 8. Translation 9. Termination 10. Future Revisions of this License How to use this License for your documents Glossary List of Figures 6-1. Lifecycle of a Bugzilla Bug List of Examples 4-1. Assigning the MySQL "root" User a Password 4-2. Disabling the MySQL "anonymous" User 4-3. Disabling Networking in MySQL 4-4. Forcing Bugzilla to output a charset B-1. Examples of urlbase/cookiepath pairs for sharing login cookies B-2. Examples of urlbase/cookiepath pairs to restrict the login cookie _________________________________________________________________Chapter 1. About This Guide1.1. Copyright Information This document is copyright (c) 2000-2005 by the various Bugzilla contributors who wrote it. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in Appendix E. If you have any questions regarding this document, its copyright, or publishing this document in non-electronic form, please contact the Bugzilla Team. _________________________________________________________________1.2. Disclaimer No liability for the contents of this document can be accepted. Follow the instructions herein at your own risk. This document may contain errors and inaccuracies that may damage your system, cause your partner to leave you, your boss to fire you, your cats to pee on your furniture and clothing, and global thermonuclear war. Proceed with caution. Naming of particular products or brands should not be seen as endorsements, with the exception of the term "GNU/Linux". We wholeheartedly endorse the use of GNU/Linux; it is an extremely versatile, stable, and robust operating system that offers an ideal operating environment for Bugzilla. Although the Bugzilla development team has taken great care to ensure that all exploitable bugs have been fixed, security holes surely exist in any piece of code. Great care should be taken both in the installation and usage of this software. The Bugzilla development team members assume no liability for your use of Bugzilla. You have the source code, and are responsible for auditing it yourself to ensure your security needs are met. _________________________________________________________________1.3. New Versions This is the 2.18.3 version of The Bugzilla Guide. It is so named to match the current version of Bugzilla. The latest version of this guide can always be found at http://www.bugzilla.org, or checked out via CVS by following the Mozilla CVS instructions and check out the mozilla/webtools/bugzilla/docs/ subtree. However, you should read the version which came with the Bugzilla release you are using. The Bugzilla Guide, or a section of it, is also available in the following languages: German. In addition, there are Bugzilla template localisation projects in the following languages. They may have translated documentation available: Belarusian, Brazilian Portuguese, Chinese, French, German, Korean, Russian and Spanish. If you would like to volunteer to translate the Guide into additional languages, please contact Dave Miller. _________________________________________________________________1.4. Credits The people listed below have made enormous contributions to the creation of this Guide, through their writing, dedicated hacking efforts, numerous e-mail and IRC support sessions, and overall excellent contribution to the Bugzilla community: Matthew P. Barnson <mbarnson@sisna.com> for the Herculaean task of pulling together the Bugzilla Guide and shepherding it to 2.14. Terry Weissman <terry@mozilla.org> for initially writing Bugzilla and creating the README upon which the UNIX installation documentation is largely based. Tara Hernandez <tara@tequilarists.org> for keeping Bugzilla development going strong after Terry left mozilla.org and for running landfill. Dave Lawrence <dkl@redhat.com> for providing insight into the key differences between Red Hat's customized Bugzilla. Dawn Endico <endico@mozilla.org> for being a hacker extraordinaire and putting up with Matthew's incessant questions and arguments on irc.mozilla.org in #mozwebtools Jacob Steenhagen <jake@bugzilla.org> for taking over documentation during the 2.17 development period. Dave Miller <justdave@bugzilla.org> for taking over as project lead when Tara stepped down and continually pushing for the documentation to be the best it can be. Thanks also go to the following people for significant contributions to this documentation: Kevin Brannen, Vlad Dascalu, Ben FrantzDale, Eric Hanson, Zach Lipton, Gervase Markham, Andrew Pearson, Joe Robins, Spencer Smith, Ron Teitelbaum, Shane Travis, Martin Wulffeld. Also, thanks are due to the members of the netscape.public.mozilla.webtools newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened. _________________________________________________________________1.5. Document Conventions This document uses the following conventions: Descriptions Appearance Warning Caution Don't run with scissors! Hint Tip Would you like a breath mint? Note Note Dear John... Information requiring special attention Warning Read this or the cat gets it. File or directory name filename Command to be typed command Application name application Normal user's prompt under bash shell bash$ Root user's prompt under bash shell bash# Normal user's prompt under tcsh shell tcsh$ Environment variables VARIABLE Term found in the glossary Bugzilla Code example<para>Beginning and end of paragraph</para> This documentation is maintained in DocBook 4.1.2 XML format. Changes are best submitted as plain text or XML diffs, attached to a bug filed in the Bugzilla Documentation component. _________________________________________________________________Chapter 2. Installing Bugzilla2.1. Installation Note If you just want to use Bugzilla, you do not need to install it. None of this chapter is relevant to you. Ask your Bugzilla administrator for the URL to access it over the web. The Bugzilla server software is usually installed on Linux or Solaris. If you are installing on another OS, check Section 2.4 before you start your installation to see if there are any special instructions. As an alternative to following these instructions, you may wish to try Arne Schirmacher's unofficial and unsupported Bugzilla Installer, which installs Bugzilla and all its prerequisites on Linux or Solaris systems. This guide assumes that you have administrative access to the Bugzilla machine. It not possible to install and run Bugzilla itself without administrative access except in the very unlikely event that every single prerequisite is already installed. Warning The installation process may make your machine insecure for short periods of time. Make sure there is a firewall between you and the Internet. You are strongly recommended to make a backup of your system before installing Bugzilla (and at regular intervals thereafter :-).
?? 快捷鍵說明
復制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -