- 2.1. What is Bugzilla?Installation
- 2.2. Why use a bug-tracking system?Configuration
- 2.3. Why use Bugzilla?Optional Additional Configuration
- 2.4. OS-Specific Installation Notes
- 2.5. Troubleshooting
- 3.1. IntroductionBugzilla Configuration
- 3.2. Create a Bugzilla AccountUser Administration
- 3.3. Anatomy of a BugProducts
- 3.4. Searching for BugsComponents
- 3.5. Bug ListsVersions
- 3.6. Filing BugsMilestones
- 3.7. Patch ViewerVoting
- 3.8. Hints and TipsGroups and Group Security
- 3.9. User Preferences
- 3.10. ReportsUpgrading to New Releases
- 4.1. Step-by-step InstallTemplate Customization
- 4.2. HTTP Server ConfigurationTemplate Hooks
- 4.3. Optional Additional ConfigurationCustomizing Who Can Change What
- 4.4. OS Specific Installation NotesModifying Your Running System
- 4.5. Bugzilla SecurityMySQL Bugzilla Database Introduction
- 4.6. TroubleshootingIntegrating Bugzilla with Third-Party Tools
- 5.1. Bugzilla ConfigurationIntroduction
- 5.2. User AdministrationCreate a Bugzilla Account
- 5.3. ProductsAnatomy of a Bug
- 5.4. ComponentsSearching for Bugs
- 5.5. VersionsBug Lists
- 5.6. MilestonesFiling Bugs
- 5.7. VotingPatch Viewer
- 5.8. Groups and Group SecurityHints and Tips
- 5.9. Upgrading to New Releases
- 6.1. Template Customization
- 6.2. Customizing Who Can Change What
- 6.3. Modifying Your Running System
- 6.4. MySQL Bugzilla Database IntroductionUser Preferences
- 6.5. Integrating Bugzilla with Third-Party Tools5.10. Reports
- C.1. Instructions
- C.2. Download Locations
- List of Examples
- 4-1. Installing perl modules with CPAN
- 5-1. 3-1. Upgrading using CVS
- 5-2. 3-2. Upgrading using the tarball
- 5-3. 3-3. Upgrading using patches 1.1. Copyright Information
- 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.
+
Powerful searching
-
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.
+
User-configurable email notifications of bug changes
- 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.
+
Full change history
Inter-bug dependency tracking and graphing
- The installation process may make your machine insecure for + short periods of time. Make sure there is a firewall between you + and the Internet. +
Excellent attachment management
-
You are strongly recommended to make a backup of your system
+ before installing Bugzilla (and at regular intervals thereafter :-).
+
Integrated, product-based, granular security schema
In outline, the installation proceeds as follows:
+ Fully security-audited, and runs under Perl's taint mode
Install Perl + (5.6.0 or above) +A robust, stable RDBMS back-end
Install MySQL + (3.23.41 or above) +Completely customisable and/or localisable web user - interface
Install a Webserver +Additional XML, email and console interfaces
Install Bugzilla +Extensive configurability
Install Perl modules +Smooth upgrade pathway between versions
Configure all of the above. +
- Click the - "Open a new Bugzilla account" - - link, enter your email address and, optionally, your name in the - spaces provided, then click - "Create Account" - - .
-
If you don't have it and your OS doesn't provide official packages,
+ visit http://www.mysql.com. You need MySQL version
+ 3.23.41 or higher.
+
Within moments, you should receive an email to the address - you provided, which contains your login name (generally the - same as the email address), and a password. - This password is randomly generated, but can be - changed to something more memorable.
Click the - "Log In" - link in the footer at the bottom of the page in your browser, - enter your email address and password into the spaces provided, and - click - "Login" Many of the binary + versions of MySQL store their data files in + /var. -
configure.You are now logged in. Bugzilla uses cookies to remember you are - logged in so, unless you have cookies disabled or your IP address changes, - you should not have to log in again.
If you install from something other than a packaging/installation + system (such as .rpm, .dep, .exe, or .msi) make sure the MySQL server + is started when the machine boots. + - You have freedom of choice here, pretty much any web server that
+ is capable of running CGI
+ scripts will work.
+ However, we strongly recommend using the Apache web server
+ (either 1.3.x or 2.x), and
+ the installation instructions usually assume you are
+ using it. If you have got Bugzilla working using another webserver,
+ please share your experiences with us by filing a bug in Bugzilla Documentation.
+
If you don't have Apache and your OS doesn't provide official packages, + visit http://httpd.apache.org/. +
AppConfig (1.52) +
Status and Resolution: - - These define exactly what state the bug is in - from not even - being confirmed as a bug, through to being fixed and the fix - confirmed by Quality Assurance. The different possible values for - Status and Resolution on your installation should be documented in the - context-sensitive help for those items.
CGI (2.93) +Assigned To: - The person responsible for fixing the bug.
Data::Dumper (any) +*URL: - A URL associated with the bug, if any.
Date::Format (2.21) +Summary: - A one-sentence summary of the problem.
DBI (1.32) +*Status Whiteboard: DBD::mysql - (a.k.a. Whiteboard) A free-form text area for adding short notes - and tags to a bug.
*Keywords: - The administrator can define keywords which you can use to tag and - categorise bugs - e.g. The Mozilla Project has keywords like crash - and regression.
File::Spec (0.82) +Platform and OS: - These indicate the computing environment where the bug was - found.
File::Temp (any) +Version: Template - The "Version" field is usually used for versions of a product which - have been released, and is set to indicate which versions of a - Component have the particular problem the bug report is - about.
Priority: - The bug assignee uses this field to prioritise his or her bugs. - It's a good idea not to change this on other people's bugs.
Text::Wrap (2001.0131) +Severity:
*Target: GD - (a.k.a. Target Milestone) A future version by which the bug is to - be fixed. e.g. The Bugzilla Project's milestones for future - Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are not - restricted to numbers, thought - you can use any text strings, such - as dates.
Reporter: Chart::Base - The person who filed the bug.
CC list: GD::Graph - A list of people who get mail when the bug changes.
Attachments: GD::Text::Align - You can attach files (e.g. testcases or patches) to bugs. If there - are any attachments, they are listed in this section.
*Dependencies: XML::Parser - If this bug cannot be fixed unless other bugs are fixed (depends - on), or this bug stops other bugs being fixed (blocks), their - numbers are recorded here.
*Votes: PatchReader - Whether this bug has any votes.
Additional Comments: MIME::Parser - You can add your two cents to the bug discussion here, if you have - something worthwhile to say.
Go to - Landfill - in your browser and click - Enter a new bug report. -
Select a product - any one will do.
Fill in the fields. Bugzilla should have made reasonable - guesses, based upon your browser, for the "Platform" and "OS" - drop-down boxes. If they are wrong, change them.
Select "Commit" and send in your bug report.
To disable the anonymous user account + and set a password for the root user, execute the following. The + root user password should be different to the bugs user password + you set in + localconfig in the previous section, + and also different to + the password for the system root account on your machine. +
bug 12345 comment 7 bug 23456, comment 53 attachment 4321 mailto:george@example.com george@example.com ftp://ftp.mozilla.org bash$ mysql mysql + mysql> DELETE FROM user WHERE user = ''; + mysql> UPDATE user SET password = password('new_password') WHERE user = 'root'; + mysql> FLUSH PRIVILEGES;From this point forward, to run the + mysql command-line client, + you will need to type + mysql -u root -p and enter + new_password when prompted. +
If you run MySQL on the same machine as your web server, you + should disable remote access to MySQL by adding + the following to your /etc/my.conf: +
Most other sorts of URL [myslqd] + # Prevent network access to MySQL. + skip-networking
- - Consult the documentation that came with your system for + information on making mysqld run as an + unprivileged user. +
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. -
For added security, you could also run MySQL, or even all + of Bugzilla + in a chroot jail; however, instructions for doing that are beyond + the scope of this document. +
This document is copyright (c) 2000-2004 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 @@ -522,29 +478,10 @@ VALIGN="TOP" Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in Appendix CAppendix D. | ||
| --Copyright (c) 2000-2004 The Bugzilla Team |
If you have any questions regarding this document, its copyright, or publishing this document in non-electronic form, @@ -578,10 +515,10 @@ NAME="disclaimer"
Although the Bugzilla development team has taken great care to - ensure that all exploitable bugs or options have been - fixed, security holes surely exist. Great care should be taken both in + 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 this software. You have + 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 VersionsThis is the 2.17.5 version of The Bugzilla Guide. It is so named +> This is the 2.17.7 version of The Bugzilla Guide. It is so named to match the current version of Bugzilla. This version of the guide, like its associated Bugzilla version, is a @@ -607,8 +544,8 @@ NAME="newversions" HREF="http://www.bugzilla.org" TARGET="_top" >http://www.bugzilla.org, or checked out via CVS. - (Please follow the , or checked out via CVS by + following the Mozilla @@ -618,12 +555,68 @@ TARGET="_top" CLASS="filename" >mozilla/webtools/bugzilla/docs/ - subtree.) However, you should read the version + subtree. However, you should read the version which came with the Bugzilla release you are using.
The Bugzilla Guide is currently only available in English. - If you would like to volunteer to translate it, please contact +> 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 Matthew P. Barnson, Kevin Brannen, Dawn Endico, Ben FrantzDale, Eric Hanson, Tara Hernandez, Dave Lawrence, Zach Lipton, Gervase Markham, Andrew Pearson, Joe Robins, Spencer Smith, Jacob Steenhagen, Ron Teitelbaum, Terry Weissman, Martin Wulffeld.
Last but not least, all the members of the
+>
Also, thanks are due to the members of the
Bugzilla is a bug- or issue-tracking system. Bug-tracking
- systems allow individual or groups of developers effectively to keep track
- of outstanding problems with their products.
- Do we need more here? Those who do not use a bug-tracking system tend to rely on
- shared lists, email, spreadsheets and/or Post-It notes to monitor the
- status of defects. This procedure
- is usually error-prone and tends to cause those bugs judged least
- significant by developers to be dropped or ignored. Integrated defect-tracking systems make sure that nothing gets
- swept under the carpet; they provide a method of creating, storing,
- arranging and processing defect reports and enhancement requests. 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.
+ Bugzilla is the leading open-source/free software bug tracking
- system. It boasts many advanced features, including:
- Bugzilla is very adaptable to various situations. Known uses
- currently include IT support queues, Systems Administration deployment
- management, chip design and development problem tracking (both
- pre-and-post fabrication), and software and hardware bug tracking for
- luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems.
- Combined with systems such as
- CVS,
- Bonsai, or
- Perforce SCM, Bugzilla
- provides a powerful, easy-to-use configuration management solution. This section contains information for end-users of Bugzilla.
- There is a Bugzilla test installation, called
- Installed Version Test: perl -v Any machine that doesn't have Perl on it is a sad machine indeed.
+ If you don't have it and your OS doesn't provide official packages,
+ visit Landfill,
- which you are welcome to play with (if it's up.)
- However, it does not necessarily
- have all Bugzilla features enabled, and runs an up-to-the-minute version,
- so some things may not quite work as this document describes. If you want to use Bugzilla, first you need to create an account.
- Consult with the administrator responsible for your installation of
- Bugzilla for the URL you should use to access it. If you're
- test-driving Bugzilla, use this URL:
- http://landfill.bugzilla.org/bugzilla-tip/.
- Installed Version Test: mysql -V The core of Bugzilla is the screen which displays a particular
- bug. It's a good place to explain some Bugzilla concepts.
-
Bug 1 on Landfill
-
- is a good example. Note that the labels for most fields are hyperlinks;
- clicking them will take you to context-sensitive help on that
- particular field. Fields marked * may not be present on every
- installation of Bugzilla.
Download a Bugzilla tarball (or check it out from CVS) and place
+ it in a suitable directory, writable by the default web server user
+ (probably "nobody").
+ Good locations are either directly in the main web space for your
+ web server or perhaps in
+ /usr/local
+ with a symbolic link from the web space.
+
Product and Component:
- Bugs are divided up by Product and Component, with a Product
- having one or more Components in it. For example,
- bugzilla.mozilla.org's "Bugzilla" Product is composed of several
- Components:
- The default Bugzilla distribution is not designed to be placed
+ in a cgi-bin directory. This
+ includes any directory which is configured using the
+ ScriptAlias directive of Apache.
+ Once all the files are in a web accessible directory, make that
+ directory writable by your webserver's user. This is a temporary step
+ until you run the
+ checksetup.pl
- The installation process of Bugzilla. Bugzilla's installation process is based
+ on a script called checksetup.pl.
+ The first thing it checks is whether you have appropriate
+ versions of all the required
+ Perl modules. The aim of this section is to pass this check.
+ When it passes,
+ do not run it again,
+ but proceed to Section 2.2.
+
At this point, you need to su to root. You should
+ remain as root until the end of the install. Then run:
+
checksetup.pl will print out a list of the
+ required and optional Perl modules, together with the versions
+ (if any) installed on your machine.
+ The list of required modules is reasonably long; however, you
+ may already have several of them installed.
+
There is a meta-module called Bundle::Bugzilla,
+ which installs all the other
+ modules with a single command. You should use this if you are running
+ Perl 5.6.1 or above.
+
The preferred way of installing Perl modules is via CPAN on Unix,
+ or PPM on Windows (see Section 2.4.1.2). These
+ instructions assume you are using CPAN; if for some reason you need
+ to install the Perl modules manually, see
+ Appendix C.
+
If you using Bundle::Bugzilla, invoke the magic CPAN command on it.
+ Otherwise, you need to work down the
+ list of modules that checksetup.pl says are
+ required, in the order given, invoking the command on each.
+ Many people complain that Perl modules will not install for
+ them. Most times, the error messages complain that they are missing a
+ file in
+ "@INC".
+ Virtually every time, this error is due to permissions being set too
+ restrictively for you to compile Perl modules or not having the
+ necessary Perl development libraries installed on your system.
+ Consult your local UNIX systems administrator for help solving these
+ permissions issues; if you
+ are
- General issues having to do with the user interface cosmetics (not
- functionality) including cosmetic issues, HTML templates,
- etc.
Here is a complete list of modules and their minimum versions.
+ Some modules have special installation notes, which follow.
+ Required Perl modules:
+ The Bugzilla Search page is is the interface where you can find
- any bug report, comment, or patch currently in the Bugzilla system. You
- can play with it here:
- http://landfill.bugzilla.org/bugzilla-tip/query.cgi. The Search page has controls for selecting different possible
- values for all of the fields in a bug, as described above. For some
- fields, multiple values can be selected. In those cases, Bugzilla
- returns bugs where the content of the field matches any one of the selected
- values. If none is selected, then the field can take any value. Once you've run a search, you can save it as a Saved Search, which
- appears in the page footer. Highly advanced querying is done using Boolean Charts. See the
- Boolean Charts help link on the Search page for more information. If you run a search, a list of matching bugs will be returned.
- The format of the list is configurable. For example, it can be
- sorted by clicking the column headings. Other useful features can be
- accessed using the links at the bottom of the list:
- The Perl GD module requires some other libraries that may or
+ may not be installed on your system, including
+ libpng
-
- change the bug attributes which appear in the list. The version of the GD module you need is very closely tied
+ to the libgd version installed on your system.
+ If you have a version 1.x of libgd the 2.x
+ versions of the GD module won't work for you.
+ 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 test bug is as follows: Try to make sure that everything said in the summary is also
- said in the first comment. Summaries are often updated and this will
- ensure your original information is easily accessible.
-
You do not need to put "any" or similar strings in the URL field.
- If there is no specific URL associated with the bug, leave this
- field blank.
- If you feel a bug you filed was incorrectly marked as a
- DUPLICATE of another, please question it in your bug, not
- the bug it was duped to. Feel free to CC the person who duped it
- if they are not already CCed.
- Viewing and reviewing patches in Bugzilla is often difficult due to
- lack of context, improper format and the inherent readability issues that
- raw patches present. Patch Viewer is an enhancement to Bugzilla designed
- to fix that by offering increased context, linking to sections, and
- integrating with Bonsai, LXR and CVS. Patch viewer allows you to: The main way to view a patch in patch viewer is to click on the
- "Diff" link next to a patch in the Attachments list on a bug. You may
- also do this within the edit window by clicking the "View Attachment As
- Diff" button in the Edit Attachment screen. To see the difference between two patches, you must first view the
- newer patch in Patch Viewer. Then select the older patch from the
- dropdown at the top of the page ("Differences between [dropdown] and
- this patch") and click the "Diff" button. This will show you what
- is new or changed in the newer patch. To get more context in a patch, you put a number in the textbox at
- the top of Patch Viewer ("Patch / File / [textbox]") and hit enter.
- This will give you that many lines of context before and after each
- change. Alternatively, you can click on the "File" link there and it
- will show each change in the full context of the file. This feature only
- works against files that were diffed using "cvs diff". To view only a certain set of files in a patch (for example, if a
- patch is absolutely huge and you want to only review part of it at a
- time), you can click the "(+)" and "(-)" links next to each file (to
- expand it or collapse it). If you want to collapse all files or expand
- all files, you can click the "Collapse All" and "Expand All" links at the
- top of the page. To link to a section of a patch (for example, if you want to be
- able to give someone a URL to show them which part you are talking
- about) you simply click the "Link Here" link on the section header. The
- resulting URL can be copied and used in discussion. (Copy Link
- Location in Mozilla works as well.) Poorly-configured MySQL and Bugzilla installations have
+ given attackers full access to systems in the past. Please take the
+ security parts of these guidelines seriously, even for Bugzilla
+ machines hidden away behind your firewall. To go to Bonsai to get blame for the lines you are interested in,
- you can click the "Lines XX-YY" link on the section header you are
- interested in. This works even if the patch is against an old
- version of the file, since Bonsai stores all versions of the file. To go to LXR, you click on the filename on the file header
- (unfortunately, since LXR only does the most recent version, line
- numbers are likely to rot). Load this file in your editor. The only value you
+ need to change is $db_pass, the password for
+ the user you will create for your database.
+ Pick a strong password (for simplicity, it should not contain
+ single quote characters) and put it here.
+
The other options in the localconfig file
+ are documented by their accompanying comments. If you have a slightly
+ non-standard MySQL setup, you may wish to change one or more of
+ the other "$db_*" parameters.
+
You may also wish to change the names of
+ the priorities, severities, operating systems and platforms for your
+ installation. However, you can always change these after installation
+ has finished; if you then re-run
+ checksetup.pl, the changes will get picked up.
+ This section distills some Bugzilla tips and best practices
- that have been developed. Bugzilla comments are plain text - so typing <U> will
- produce less-than, U, greater-than rather than underlined text.
- However, Bugzilla will automatically make hyperlinks out of certain
- sorts of text in comments. For example, the text
- "http://www.bugzilla.org" will be turned into a link:
- http://www.bugzilla.org.
- Other strings which get linkified in the obvious manner are:
- Quicksearch is a single-text-box query tool which uses
- metacharacters to indicate what is to be searched. For example, typing
- "foo|bar"
- into Quicksearch would search for "foo" or "bar" in the
- summary and status whiteboard of a bug; adding
- "You need to configure MySQL to accept large packets, if you
+ want to have attachments larger than 64K. Add the text
+ below to your
+ :BazProduct" would
- search only in that product.
- You'll find the Quicksearch box on Bugzilla's
- front page, along with a
- Help
- link which details how to use it. If you are changing the fields on a bug, only comment if
- either you have something pertinent to say, or Bugzilla requires it.
- Otherwise, you may spam people unnecessarily with bug mail.
- To take an example: a user can set up their account to filter out messages
- where someone just adds themselves to the CC field of a bug
- (which happens a lot.) If you come along, add yourself to the CC field,
- 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.
-
Use attachments, rather than comments, for large chunks of ASCII data,
- such as trace, debugging output files, or log files. That way, it doesn't
- bloat the bug for everyone who wants to read it, and cause people to
- receive fat, useless mails.
- Trim screenshots. There's no need to show the whole screen if
- you are pointing out a single-pixel problem.
- Don't attach simple test cases (e.g. one HTML file, one
- CSS file and an image) as a ZIP file. Instead, upload them in
- reverse order and edit the referring file so that they point to the
- attached files. This way, the test case works immediately
- out of the bug.
- Once you have logged in, you can customise various aspects of
- Bugzilla via the "Edit prefs" link in the page footer.
- The preferences are split into three tabs: On this tab, you can change your basic account information,
- including your password, email address and real name. For security
- reasons, in order to change anything on this page you must type your
- currentWe use an SQL GRANT command to create a
+ "bugs"
- password into the
- "Password""bugs"
- field at the top of the page.
- If you attempt to change your email address, a confirmation
- email is sent to both the old and new addresses, with a link to use to
- confirm the change. This helps to prevent account hijacking. On this tab you can reduce or increase the amount of email sent
- you from Bugzilla, opting in our out depending on your relationship to
- the bug and the change that was made to it.
-
You can also do further filtering on the client side by
- using the X-Bugzilla-Reason mail header which Bugzilla
- adds to all bugmail. This tells you what relationship you have to the
- bug in question,
- and can be any of Owner, Reporter, QAcontact, CClist, Voter and
- WatchingComponent. By entering user email names, delineated by commas, into the
- "Users to watch" text entry box you can receive a copy of all the
- bugmail of other users (security settings permitting.) This powerful
- functionality enables seamless transitions as developers change
- projects or users go on holiday. The ability to watch other users may not be available in all
- Bugzilla installations. If you can't see it, ask your
- administrator.Chapter 2. Introduction
Chapter 2. Installing Bugzilla2.1. What is Bugzilla?
2.2. Why use a bug-tracking system?
2.3. Why use Bugzilla?
Chapter 3. Using Bugzilla
2.1.1. Perl3.1. Introduction
3.2. Create a Bugzilla Account
2.1.3. Web Server3.3. Anatomy of a Bug
2.1.4. Bugzilla
Administration:
- Administration of a Bugzilla installation.
Bugzilla-General:
- Anything that doesn't fit in the other components, or spans
- multiple components.
Creating/Changing Bugs:
- Creating, changing, and viewing bugs.
Documentation:
- The Bugzilla documentation, including The Bugzilla Guide.
Email:
- Anything to do with email sent by Bugzilla.
Installation: 2.1.5. Perl Modules
Query/Buglist:
- Anything to do with searching for bugs and viewing the
- buglists. bash# ./checksetup.pl
Reporting/Charting:
- Getting reports from Bugzilla. bash# perl -MCPAN -e 'install "<modulename>"'
User Accounts:
- Anything about managing a user account from the user's perspective.
- Saved queries, creating accounts, changing passwords, logging in,
- etc.
User Interface:
- This indicates how severe the problem is - from blocker
- ("application unusable") to trivial ("minor cosmetic issue"). You
- can also use this field to indicate whether a bug is an enhancement
- request.3.4. Searching for Bugs
2.1.5.2. Template Toolkit (2.08)
2.1.5.3. GD (1.20)3.5. Bug Lists
Long Format:
-
- this gives you a large page with a non-editable summary of the fields
- of each bug.
CSV:
-
- get the buglist as comma-separated values, for import into e.g.
- a spreadsheet.
Change Columns: libgd.
+ The full requirements are listed in the Perl GD module README.
+ If compiling GD fails, it's probably because you're
+ missing a required library.
-
Change several bugs at once:
-
- If your account is sufficiently empowered, you can make the same
- change to all the bugs in the list - for example, changing their
- owner.
Send mail to bug owners:
-
- Sends mail to the owners of all bugs on the list.
Edit Search:
-
- If you didn't get exactly the results you were looking for, you can
- return to the Query page through this link and make small revisions
- to the query you just made so you get more accurate results.
Remember Search As:
-
- You can give a search a name and remember it; a link will appear
- in your page footer giving you quick access to run it again later.
- 3.6. Filing Bugs
3.7. Patch Viewer
2.1.5.5. GD::Graph (any)The GD::Graph module is only required if you want graphical
+ reports.
+ View patches in color, with side-by-side view rather than trying
- to interpret the contents of the patch. See the difference between two patches. Get more context in a patch. Collapse and expand sections of a patch for easy
- reading. Link to a particular section of a patch for discussion or
- review Go to Bonsai or LXR to see more context, blame, and
- cross-references for the part of the patch you are looking at Create a rawtext unified format diff out of any patch, no
- matter what format it came from
2.1.5.6. GD::Text::Align (any)3.7.1. Viewing Patches in Patch Viewer
2.1.5.7. XML::Parser (any)3.7.2. Seeing the Difference Between Two Patches
2.1.5.8. MIME::Parser (any)3.7.3. Getting More Context in a Patch
2.1.5.9. PatchReader (0.9.1)3.7.4. Collapsing and Expanding Sections of a Patch
2.2. Configuration3.7.5. Linking to a Section of a Patch
3.7.6. Going to Bonsai and LXR
2.2.2.1. Security3.8. Hints and Tips
3.8.1. Autolinkification
MySQL ships as insecure by default.
+ It allows anybody to on the local machine full administrative
+ capabilities without requiring a password; the special
+ MySQL root account (note: this is not the same as
+ the system root) also has no password.
+ Also, many installations default to running
+ mysqld as the system root.
+
2.2.2.2. Allow large attachments3.8.2. Quicksearch
[mysqld]
+ # Allow packets up to 1M
+ set-variable = max_allowed_packet=1M
3.8.3. Comments
3.8.4. Attachments
You need to add a new MySQL user for
+ Bugzilla to use. (It's not safe to have Bugzilla use the MySQL root
+ account.) The following instructions assume the defaults in
+ localconfig;
+ if you changed those, you need to modify the
+ SQL command appropriately. You will need the
+ $db_pass password you set in
+ localconfig in
+ Section 2.2.1.
+ 3.9. User Preferences
3.9.1. Account Settings
3.9.2. Email Settings
mysql> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE,
+ DROP,REFERENCES ON bugs.* TO bugs@localhost
+ IDENTIFIED BY '$db_pass';
+ mysql> FLUSH PRIVILEGES
After that, it asks for details of an administrator account. Bugzilla + can have multiple administrators - you can create more later - but + it needs one to start off with. + Enter the email address of an administrator, his or her full name, + and a suitable Bugzilla password. +
checksetup.pl will then finish. You may rerun + checksetup.pl at any time if you wish. +