IMPORTANT: this documentation is currently being + updated for the Bugzilla 2.16 release and is in an unusual state of + flux. Even more than normal, don't believe everything, + or even anything, you read. + |
Users can query Bugzilla from the command line using this suite of - utilities.
The query.conf file contains the mapping from options to field - names and comparison types. Quoted option names are "grepped" for, so it - should be easy to edit this file. Comments (#) have no effect; you must - make sure these lines do not contain any quoted "option"
buglist is a shell script which submits a Bugzilla query and writes - the resulting HTML page to stdout. It supports both short options, (such - as "-Afoo" or "-Rbar") and long options (such as "--assignedto=foo" or - "--reporter=bar"). If the first character of an option is not "-", it is - treated as if it were prefixed with "--default=".
The columlist is taken from the COLUMNLIST environment variable. - This is equivalent to the "Change Columns" option when you list bugs in - buglist.cgi. If you have already used Bugzilla, use - grep COLUMLIST ~/.netscape/cookies - - to see your current COLUMNLIST setting.
bugs is a simple shell script which calls buglist and extracts the - bug numbers from the output. Adding the prefix - "http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug list into - a working link if any bugs are found. Counting bugs is easy. Pipe the - results through - sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}' -
C.2. Command-line Bugzilla QueriesAkkana says she has good results piping buglist output through - w3m -T text/html -dump -
There are a suite of utilities for querying Bugzilla from the + command line. Although there's no particular reason why they + shouldn't work, they have not been tested with 2.16.The query.conf file contains the mapping from options to field + names and comparison types. Quoted option names are "grepped" for, so it + should be easy to edit this file. Comments (#) have no effect; you must + make sure these lines do not contain any quoted "option".
buglist is a shell script which submits a Bugzilla query and writes + the resulting HTML page to stdout. It supports both short options, (such + as "-Afoo" or "-Rbar") and long options (such as "--assignedto=foo" or + "--reporter=bar"). If the first character of an option is not "-", it is + treated as if it were prefixed with "--default=".
The columlist is taken from the COLUMNLIST environment variable. + This is equivalent to the "Change Columns" option when you list bugs in + buglist.cgi. If you have already used Bugzilla, use + grep COLUMLIST ~/.netscape/cookies + + to see your current COLUMNLIST setting.
bugs is a simple shell script which calls buglist and extracts the + bug numbers from the output. Adding the prefix + "http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug list into + a working link if any bugs are found. Counting bugs is easy. Pipe the + results through + sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}' +
Akkana says she has good results piping buglist output through + w3m -T text/html -dump +
Version 1.1, March 2000
Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place, @@ -167,7 +170,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" >PrevThe Quicksearch UtilityCopyright Information
Up Prev 0-9, high ascii
0-9, high asciiBA "Bug""bug" in Bugzilla refers to an issue entered into the database which has an @@ -174,39 +171,19 @@ CLASS="QUOTE" >
- localconfig - - file contains the password to your database. If this information were - generally available, and remote access to your database turned on, - you risk corruption of your database by computer criminals or the + file contains the password to your database. curious.
Each Bugzilla Bug is assigned a number that uniquely identifies - that Bug. The Bug associated with a Bug Number can be pulled up via a +>Each Bugzilla bug is assigned a number that uniquely identifies + that bug. The bug associated with a bug number can be pulled up via a query, or easily from the very front page by typing the number in the "Find" box.
- Bug Life Cycle
A Bug has stages through which it must pass before becoming a - "closed bug", - including acceptance, resolution, and verification. The - "Bug Life Cycle" - - is moderately flexible according to the needs of the organization - using it, though.
- Bugzilla
Bugzilla is the industry-standard bug tracking system. It is - quite popular among Open Source enthusiasts.
Bugzilla is the world-leading free software bug tracking system. +
A loop of information that never ends; see recursion.
A Product is a broad category of types of bugs. In general, - there are several Components to a Product. A Product may also define a +>A Product is a broad category of types of bugs, normally + representing a single piece of software or entity. In general, + there are several Components to a Product. A Product may define a group (used for security) for all bugs entered into - components beneath it.
The property of a function looking back at itself for - something. - "GNU", for instance, stands for - "GNU's Not UNIX", - thus recursing upon itself for definition. For further clarity, see - Infinite Loop.
This is the documentation for Bugzilla, the mozilla.org - bug-tracking system. - Bugzilla is an enterprise-class piece of software - that powers issue-tracking for hundreds of - organizations around the world, tracking millions of bugs. +> This is the documentation for Bugzilla, the mozilla.org + bug-tracking system. + Bugzilla is an enterprise-class piece of software + that powers issue-tracking for hundreds of + organizations around the world, tracking millions of bugs.
This documentation is maintained in DocBook 4.1.2 XML format. - Changes are best submitted as plain text or SGML diffs, attached - to a Bugzilla bug. +>
IMPORTANT: this documentation is currently being + updated for the Bugzilla 2.16 release and is in an unusual state of + flux. Even more than normal, don't believe everything, + or even anything, you read. + |
+ This documentation is maintained in DocBook 4.1.2 XML format. + Changes are best submitted as plain text or SGML diffs, attached + to a bug filed in + bugzilla.mozilla.org.
Bonsai is a web-based tool for managing + CVS, the Concurrent Versioning System + + . Using Bonsai, administrators can control open/closed status of trees, + query a fast relational database back-end for change, branch, and comment + information, and view changes made since the last time the tree was + closed. These kinds of changes cause the engineer responsible to be + "on the hook" + + (include cool URL link here for Hook policies at mozilla.org). Bonsai + also includes gateways to + Tinderbox, the Mozilla automated build management system + + and Bugzilla
CVS integration is best accomplished, at this point, using the + Bugzilla Email Gateway. There have been some files submitted to allow + greater CVS integration, but we need to make certain that Bugzilla is not + tied into one particular software management package.
Follow the instructions in the FAQ for enabling Bugzilla e-mail + integration. Ensure that your check-in script sends an email to your + Bugzilla e-mail gateway with the subject of + "[Bug XXXX]" + + , and you can have CVS check-in comments append to your Bugzilla bug. If + you have your check-in script include an @resolution field, you can even + change the Bugzilla bug state.
There is also a project, based upon somewhat dated Bugzilla code, + to integrate CVS and Bugzilla through CVS' ability to email. Check it out + at: + http://homepages.kcbbs.gen.nz/~tonyg/ + + , under the + "cvszilla" + + link.
You can find the project page for Bugzilla and Teamtrack Perforce + integration (p4dti) at: + http://www.ravenbrook.com/project/p4dti + + . + "p4dti" + + is now an officially supported product from Perforce, and you can find + the "Perforce Public Depot" p4dti page at + http://public.perforce.com/public/perforce/p4dti/index.html + + .
Integration of Perforce with Bugzilla, once patches are applied, is + seamless. Perforce replication information will appear below the comments + of each bug. Be certain you have a matching set of patches for the + Bugzilla version you are installing. p4dti is designed to support + multiple defect trackers, and maintains its own documentation for it. + Please consult the pages linked above for further information.
We need Tinderbox integration information.
There are a lot of common libraries and utilities out there that Apple did not include with Mac OS X, but which run perfectly well on it. diff --git a/docs/html/patches.html b/docs/html/patches.html index 5a9e53ce3b..5c58fb0464 100644 --- a/docs/html/patches.html +++ b/docs/html/patches.html @@ -72,7 +72,7 @@ WIDTH="100%">
Example 5-1. Creating some Components
The computer game you are designing may have a "UI"
@@ -358,14 +358,14 @@ NAME="versions">5.3.3. Versions Example 5-2. Common Use of Versions A user reports a bug against Version "Beta 2.0" of your
@@ -384,14 +384,14 @@ NAME="AEN1290"> Example 5-3. A Different Use of Versions This field has been used to good effect by an online service
@@ -508,14 +508,14 @@ TYPE="1"
> Example 5-4. Using SortKey with Target Milestone The concept of "voting" is a poorly understood, yet powerful
- feature for the management of open-source projects. Each user is
- assigned so many Votes per product, which they can freely reassign (or
- assign multiple votes to a single bug). This allows developers to gauge
- user need for a particular enhancement or bugfix. By allowing bugs with
- a certain number of votes to automatically move from "UNCONFIRMED" to
- "NEW", users of the bug system can help high-priority bugs garner
- attention so they don't sit for a long time awaiting triage. The daunting challenge of Votes is deciding where you draw the
- line for a "vocal majority". If you only have a user base of 100 users,
- setting a low threshold for bugs to move from UNCONFIRMED to NEW makes
- sense. As the Bugzilla user base expands, however, these thresholds
- must be re-evaluated. You should gauge whether this feature is worth
- the time and close monitoring involved, and perhaps forego
- implementation until you have a critical mass of users who demand
- it. To modify Voting settings: Navigate to the "Edit product" screen for the Product you
- wish to modify Set "Maximum Votes per person" to your calculated value.
- Setting this field to "0" disables voting. Set "Maximum Votes a person can put on a single bug" to your
- calculated value. It should probably be some number lower than the
- "Maximum votes per person". Setting this field to "0" disables
- voting, but leaves the voting options open to the user. This is
- confusing. Set "Number of votes a bug in this product needs to
- automatically get out of the UNCONFIRMED state" to your calculated
- number. Setting this field to "0" disables the automatic move of
- bugs from UNCONFIRMED to NEW. Some people advocate leaving this at
- "0", but of what use are Votes if your Bugzilla user base is unable
- to affect which bugs appear on Development radar?
- You should probably set this number to higher than a small
- coalition of Bugzilla users can influence it. Most sites use this
- as a "referendum" mechanism -- if users are able to vote a bug
- out of UNCONFIRMED, it is a
- really
-
- bad bug! Once you have adjusted the values to your preference, select
- the "Update" button. Groups can be very useful in bugzilla, because they allow users
- to isolate bugs or products that should only be seen by certain people.
- Groups can also be a complicated minefield of interdependencies and
- weirdness if mismanaged.
- Groups in Bugzilla are a complicated beast that evolved out of
- very simple user permission bitmasks, apparently itself derived from
- common concepts in UNIX access controls. A "bitmask" is a
- fixed-length number whose value can describe one, and only one, set
- of states. For instance, UNIX file permissions are assigned bitmask
- values: "execute" has a value of 1, "write" has a value of 2, and
- "read" has a value of 4. Add them together, and a file can be read,
- written to, and executed if it has a bitmask of "7". (This is a
- simplified example -- anybody who knows UNIX security knows there is
- much more to it than this. Please bear with me for the purpose of
- this note.) The only way a bitmask scheme can work is by doubling the
- bit count for each value. Thus if UNIX wanted to offer another file
- permission, the next would have to be a value of 8, then the next 16,
- the next 32, etc. Similarly, Bugzilla offers a bitmask to define group
- permissions, with an internal limit of 64. Several are already
- occupied by built-in permissions. The way around this limitation is
- to avoid assigning groups to products if you have many products,
- avoid bloating of group lists, and religiously prune irrelevant
- groups. In reality, most installations of Bugzilla support far fewer
- than 64 groups, so this limitation has not hit for most sites, but it
- is on the table to be revised for Bugzilla 3.0 because it interferes
- with the security schemes of some administrators. To enable Generic Group Security ("usebuggroups"): Turn "On" "usebuggroups" in the "Edit Parameters"
- screen. You will generally have no groups set up. Select the "groups"
- link in the footer. Take a moment to understand the instructions on the "Edit
- Groups" screen. Once you feel confident you understand what is
- expected of you, select the "Add Group" link. Fill out the "New Name" (remember, no spaces!), "New
- Description", and "New User RegExp" fields. "New User RegExp"
- allows you to automatically place all users who fulfill the Regular
- Expression into the new group.
- To enable Product-Based Group Security
- (usebuggroupsentry): Don't forget that you only have 64 groups masks available,
- total, for your installation of Bugzilla! If you plan on having more
- than 50 products in your individual Bugzilla installation, and
- require group security for your products, you should consider either
- running multiple Bugzillas or using Generic Group Security instead of
- Product-Based ("usebuggroupsentry") Group Security. Turn "On" "usebuggroups" and "usebuggroupsentry" in the "Edit
- Parameters" screen. "usebuggroupsentry" has the capacity to prevent the
- administrative user from directly altering bugs because of
- conflicting group permissions. If you plan on using
- "usebuggroupsentry", you should plan on restricting
- administrative account usage to administrative duties only. In
- other words, manage bugs with an unpriveleged user account, and
- manage users, groups, Products, etc. with the administrative
- account. You will generally have no Groups set up, unless you enabled
- "usebuggroupsentry" prior to creating any Products. To create
- "Generic Group Security" groups, follow the instructions given
- above. To create Product-Based Group security, simply follow the
- instructions for creating a new Product. If you need to add users
- to these new groups as you create them, you will find the option to
- add them to the group available under the "Edit User"
- screens. You may find this example illustrative for how bug groups work.
- Quicksearch is a new, experimental feature of the 2.12 release. It
- consist of two Javascript files, "quicksearch.js" and "localconfig.js",
- and two documentation files, "quicksearch.html" and
- "quicksearchhack.html" The index.html page has been updated to include the QuickSearch
- text box. To take full advantage of the query power, the Bugzilla maintainer
- must edit "localconfig.js" according to the value sets used in the local
+ must edit "localconfig.js" and change the parameters according to the local
installation. Currently, keywords must be hard-coded in localconfig.js. If they
@@ -161,7 +166,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
>NextGNU Free Documentation LicenseGlossary There are many, many more things you can do with mod_rewrite.
- As time goes on, I will include many more in the Guide. For now,
- though, please refer to the mod_rewrite documentation at
+ Please refer to the mod_rewrite documentation at
http://www.apache.org
+>.
Chapter 7. Bugzilla Variants and CompetitorsAppendix D. Bugzilla Variants and CompetitorsAppendix D. Useful Patches and Utilities for BugzillaAppendix C. Useful Patches and Utilities for Bugzilla5.3.5. Voting
- 5.3.6. Groups and Group Security
NextBugzilla SecurityVotingNextD.4. The Quicksearch Utility
D.3. The Quicksearch UtilityNext D.1. Apache
+NAME="rewrite">C.1. Apache
mod_rewrite
-<VirtualHost 12.34.56.78>
+>
<VirtualHost 12.34.56.78>
RewriteEngine On
RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
</VirtualHost>
-
-
Red Hat Bugzilla is probably the most popular Bugzilla variant on - the planet. One of the major benefits of Red Hat Bugzilla is the ability +>Red Hat Bugzilla is probably the most popular Bugzilla, after + Bugzilla itself, on the planet. One of the major benefits of Red Hat + Bugzilla is the ability to work with Oracle, MySQL, and PostGreSQL databases serving as the - back-end, instead of just MySQL. Dave Lawrence has worked very hard to - keep Red Hat Bugzilla up-to-date, and many people prefer the - snappier-looking page layout of Red Hat Bugzilla to the default - Mozilla-standard formatting.
URL: Prev
| Integrating Bugzilla with Third-Party Tools | Template Customisation
Bugzilla has been successfully installed under Solaris, Linux, and Win32. Win32 is not yet officially supported, but many people @@ -97,7 +97,7 @@ CLASS="section" >
The software packages necessary for the proper running of - Bugzilla are: + Bugzilla (with download links) are:
MySQL database server and the mysql client (3.22.5 or - greater)
MySQL database server + (3.22.5 or greater) +Perl (5.005 or greater, 5.6.1 is recommended if you wish to - use Bundle::Bugzilla)
Perl + (5.005 or greater, 5.6.1 is recommended if you wish to + use Bundle::Bugzilla) +Perl Modules (minimum version): -
Template (v2.07)
Template + (v2.07) +AppConfig (v1.52)
AppConfig + + (v1.52) +Text::Wrap (v2001.0131)
Text::Wrap + (v2001.0131) +File::Spec (v0.8.2)
File::Spec + + (v0.8.2) +Data::Dumper (any)
Data::Dumper + + (any) +DBD::mysql (v1.2209)
DBD::mysql + + (v1.2209) +DBI (v1.13)
DBI + (v1.13) +Date::Parse (any)
Date::Parse + + (any) +CGI::Carp (any)
CGI::Carp + (any) +GD (v1.19) for bug charting
GD + (v1.19) for bug charting +Chart::Base (v0.99c) for bug charting
Chart::Base + + (v0.99c) for bug charting +XML::Parser (any) for the XML interface
XML::Parser + (any) for the XML interface +MIME::Parser (any) for the email interface
MIME::Parser + (any) for the email interface +The web server of your choice. Apache is recommended.
The web server of your choice. + Apache + is highly recommended. +Quality, general Perl module installation instructions can be @@ -594,7 +675,7 @@ HREF="downloadlinks.html"
Untar the module tarball -- it should create its own
@@ -754,7 +835,7 @@ CLASS="section"
> The DBI module is a generic Perl module used the
MySQL-related modules. As long as your Perl installation was done
@@ -767,7 +848,7 @@ CLASS="section"
> The Data::Dumper module provides data structure persistence for
Perl (similar to Java's serialization). It comes with later
@@ -779,7 +860,7 @@ CLASS="section"
> The Perl/MySQL interface requires a few mutually-dependent Perl
modules. These modules are grouped together into the the
@@ -803,7 +884,7 @@ CLASS="section"
> Many of the more common date/time/calendar related Perl modules
have been grouped into a bundle similar to the MySQL modules bundle.
@@ -817,7 +898,7 @@ CLASS="section"
> The GD library was written by Thomas Boutell a long while ago to
programatically generate images in C. Since then it's become the
@@ -870,16 +951,11 @@ CLASS="section"
> The Chart module provides Bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it has been
- fetched from CPAN where it is found as the Chart-x.x... tarball, linked
- in
- Appendix B.
+ fetched from CPAN.
Note that earlier versions that 0.99c used GIFs, which are no longer
supported by the latest versions of GD.4.1.5.1. DBI
4.1.5.1. DBI4.1.5.2. Data::Dumper
4.1.5.2. Data::Dumper4.1.5.3. MySQL-related modules
4.1.5.3. MySQL-related modules4.1.5.4. TimeDate modules
4.1.5.4. TimeDate modules4.1.5.5. GD (optional)
4.1.5.5. GD (optional)4.1.5.6. Chart::Base (optional)
4.1.5.6. Chart::Base (optional)
You have a freedom of choice here - Apache, Netscape or any other server on UNIX would do. You can run the web server on a @@ -1064,7 +1140,7 @@ CLASS="section" >
You should untar the Bugzilla files into a directory that you're willing to make writable by the default web server user (probably @@ -1139,23 +1215,14 @@ CLASS="filename" >/usr/bin/perl). Otherwise you must hack all the .cgi files to change where they look - for Perl. This can be done using - The setperl.csh Utility, - found in - Useful Patches and Utilities for Bugzilla, or the below one-liner. + for Perl. This can be done using the following Perl one-liner. I suggest using the symlink approach for future release compatibility.
Example 4-1. Changing the path to Perl
After you've gotten all the software installed and working you're ready to start preparing the database for its life as the back end to @@ -1363,7 +1430,7 @@ CLASS="section" >
If you followed the installation instructions for setting up your "bugs" and "root" user in MySQL, much of this should not apply to you. @@ -1787,156 +1856,6 @@ TYPE="1" >
By now you have a fully functional Bugzilla, but what good are - bugs if they're not annoying? To help make those bugs more annoying you - can set up Bugzilla's automatic whining system to complain at engineers - which leave their bugs in the NEW state without triaging them. -
This can be done by - adding the following command as a daily crontab entry (for help on that - see that crontab man page): -
| cd <your-bugzilla-directory> ; - ./whineatnews.pl - - |
Depending on your system, crontab may have several manpages. - The following command should lead you to the most useful page for - this purpose: -
|
As long as you installed the GD and Graph::Base Perl modules you - might as well turn on the nifty Bugzilla bug reporting graphs.
Add a cron entry like this to run - collectstats.pl - daily at 5 after midnight: -
| bash# - - crontab -e - - |
| 5 0 * * * cd <your-bugzilla-directory> ; - ./collectstats.pl - |
After two days have passed you'll be able to view bug graphs from - the Bug Reports page.
Fenris was a fork from Bugzilla made by Loki Games; when Loki went into receivership, it died. While Loki's other code lives on, diff --git a/docs/html/variant-issuezilla.html b/docs/html/variant-issuezilla.html index 4e3614fef4..e14cc07946 100644 --- a/docs/html/variant-issuezilla.html +++ b/docs/html/variant-issuezilla.html @@ -53,7 +53,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Chapter 7. Bugzilla Variants and Competitors
Issuezilla was another fork from Bugzilla, made by collab.net and hosted at tigris.org. It is also dead; the primary focus of bug-tracking diff --git a/docs/html/variant-perforce.html b/docs/html/variant-perforce.html index 95b96329a6..bba15e9b3b 100644 --- a/docs/html/variant-perforce.html +++ b/docs/html/variant-perforce.html @@ -53,7 +53,7 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Chapter 7. Bugzilla Variants and Competitors
Although Perforce isn't really a bug tracker, it can be used as such through the Chapter 7. Bugzilla Variants and Competitors
Scarab is a new bug-tracking system built using Java +>Scarab is a new open source bug-tracking system built using Java Serlet technology. It is currently at version 1.0 beta 7.
URL: diff --git a/docs/html/variant-sourceforge.html b/docs/html/variant-sourceforge.html index 906c3ecaf8..1e4891f4a9 100644 --- a/docs/html/variant-sourceforge.html +++ b/docs/html/variant-sourceforge.html @@ -16,8 +16,8 @@ REL="PREVIOUS" TITLE="Perforce SCM" HREF="variant-perforce.html">
Chapter 7. Bugzilla Variants and CompetitorsSourceForge is a way of coordinating geographically distributed free software and open source projects over the Internet. @@ -121,7 +121,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" >NextThe Bugzilla FAQGlossary
PrevThis section covers installation on Microsoft Windows 95, 98, ME, NT, and 2000. Bugzilla works fine on Win32 platforms, but please remember @@ -102,7 +102,7 @@ CLASS="section" >
Example 4-2. Installing ActivePerl ppd Modules on Microsoft
Windows Example 4-3. Installing OpenInteract ppd Modules manually on Microsoft
Windows From Andrew Pearson:
You can make Bugzilla work with Personal Web Server for
@@ -1616,7 +1616,7 @@ VALIGN="TOP"
What follows is some late-breaking information on using the LDAP
- authentication options with Bugzilla. The author has not tested these
- (nor even formatted this section!) so please contribute feedback to the
- newsgroup. Mozilla::LDAP module The Mozilla::LDAP module allows you4.2.2. Additional Windows Tips
4.3.2. Additional Windows Tips4.2.3. Bugzilla LDAP Integration
- to use LDAP for authentication to the Bugzilla system. This module is
- not required if you are not using LDAP. Mozilla::LDAP (aka PerLDAP) is
- available for download from http://www.mozilla.org/directory. NOTE: The
- Mozilla::LDAP module requires Netscape's Directory SDK. Follow the link
- for "Directory SDK for C" on that same page to download the SDK first.
- After you have installed this SDK, then install the PerLDAP module.
- ----------------------------------------------------------------------
- Post-Installation Checklist
- ----------------------------------------------------------------------
- Set useLDAP to "On" **only** if you will be using an LDAP directory for
- authentication. Be very careful when setting up this parameter; if you
- set LDAP authentication, but do not have a valid LDAP directory set up,
- you will not be able to log back in to Bugzilla once you log out. (If
- this happens, you can get back in by manually editing the data/params
- file, and setting useLDAP back to 0.) If using LDAP, you must set the
- three additional parameters: Set LDAPserver to the name (and optionally
- port) of your LDAP server. If no port is specified, it defaults to the
- default port of 389. (e.g "ldap.mycompany.com" or
- "ldap.mycompany.com:1234") Set LDAPBaseDN to the base DN for searching
- for users in your LDAP directory. (e.g. "ou=People,o=MyCompany") uids
- must be unique under the DN specified here. Set LDAPmailattribute to
- the name of the attribute in your LDAP directory which contains the
- primary email address. On most directory servers available, this is
- "mail", but you may need to change this.
- ----------------------------------------------------------------------
- (Not sure where this bit should go, but it's important that it be in
- there somewhere...)
- ----------------------------------------------------------------------
- Using LDAP authentication for Bugzilla: The existing authentication
- scheme for Bugzilla uses email addresses as the primary user ID, and a
- password to authenticate that user. All places within Bugzilla where
- you need to deal with user ID (e.g assigning a bug) use the email
- address. The LDAP authentication builds on top of this scheme, rather
- than replacing it. The initial log in is done with a username and
- password for the LDAP directory. This then fetches the email address
- from LDAP and authenticates seamlessly in the standard Bugzilla
- authentication scheme using this email address. If an account for this
- address already exists in your Bugzilla system, it will log in to that
- account. If no account for that email address exists, one is created at
- the time of login. (In this case, Bugzilla will attempt to use the
- "displayName" or "cn" attribute to determine the user's full name.)
- After authentication, all other user-related tasks are still handled by
- email address, not LDAP username. You still assign bugs by email
- address, query on users by email address, etc.
- ----------------------------------------------------------------------
This is simply a group to play with+
.*@mydomain.tld+
This is simply a group to play with+ + , and a New User RegExp of +
.*@mydomain.tld+ + . This new group automatically includes all Bugzilla users with + "@mydomain.tld" at the end of their user id. When I finished, + my new group was assigned bit #128.
This is simply a group to play with+
.*@mydomain.tld+
This is simply a group to play with+ + , and a New User RegExp of +
.*@mydomain.tld+ + . This new group automatically includes all Bugzilla users with + "@mydomain.tld" at the end of their user id. When I finished, + my new group was assigned bit #128.