Confirmed users, Bureaucrats and Sysops emeriti
674
edits
Bugzilla:FAQ: Difference between revisions
→Do users have to have any particular type of email application?: Email is no longer necessarily plaintext. credit to Zangune on irc
(→For Users: Update this section to be current and remove questions that are no longer relevant) |
(→Do users have to have any particular type of email application?: Email is no longer necessarily plaintext. credit to Zangune on irc) |
||
| (21 intermediate revisions by 9 users not shown) | |||
| Line 1: | Line 1: | ||
This is a list of the most-frequently-asked questions about Bugzilla. | |||
If you edit this page, please only add questions that are '''frequently asked'''. Questions that are less-commonly-asked should just get their own Wiki page. | |||
=General Questions= | =General Questions= | ||
| Line 29: | Line 33: | ||
We think that compared to other bug-tracking systems, Bugzilla offers superior performance on commodity hardware, better price (free!), more developer-friendly features (such as stored queries, email integration, and platform independence), improved scalability, greater flexibility, and superior ease-of-use under long-term usage. | We think that compared to other bug-tracking systems, Bugzilla offers superior performance on commodity hardware, better price (free!), more developer-friendly features (such as stored queries, email integration, and platform independence), improved scalability, greater flexibility, and superior ease-of-use under long-term usage. | ||
==Which versions support MySQL, PostgreSQL and | ==Which versions support MySQL, PostgreSQL, Oracle and SQLite? What about Sybase/Msql/MSSQL?== | ||
Bugzilla 3.2 and above support MySQL, PostgreSQL and Oracle. Since Bugzilla 4.2, SQLite is also supported, but its support remains experimental. Support for MS-SQL is currently under way for a future version of Bugzilla. | |||
Sybase support is no longer being worked on, and most likely will never happen, as Sybase lacks many features Bugzilla needs. | Sybase support is no longer being worked on, and most likely will never happen, as Sybase lacks many features Bugzilla needs. | ||
| Line 49: | Line 50: | ||
to something else: | to something else: | ||
perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl contrib/*pl | perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl contrib/*pl extensions/*pl | ||
If your perl path is something else again, | If your perl path is something else again, | ||
| Line 96: | Line 97: | ||
==Do users have to have any particular type of email application?== | ==Do users have to have any particular type of email application?== | ||
No. Bugzilla email | No. Bugzilla can send email in plain text, the most compatible mail format on the planet. HTML email is available for people who want it formatted in a more readable fashion. The site admin can choose which format is default, but each user can change it from the default also. | ||
==Does Bugzilla allow data to be imported and exported? (Say, from/to Word or Excel.) == | ==Does Bugzilla allow data to be imported and exported? (Say, from/to Word or Excel.) == | ||
| Line 113: | Line 114: | ||
You should use the commands included with your database software to run the backups of your Bugzilla data. | You should use the commands included with your database software to run the backups of your Bugzilla data. | ||
You can find strategies for dealing with backup considerations at | You can find strategies for dealing with backup considerations at | ||
https://dev.mysql.com/doc/mysql-enterprise-backup/en/mysqlbackup.tasks.html for MySQL and at | |||
http://www.postgresql.org/docs/8.0/static/backup.html for PostgreSQL. | http://www.postgresql.org/docs/8.0/static/backup.html for PostgreSQL. | ||
| Line 139: | Line 140: | ||
=Administrative Questions= | =Administrative Questions= | ||
==Does Bugzilla provide record locking when there is simultaneous access to the same bug? Does the second person get a notice that the bug is in use or how are they notified?== | ==Does Bugzilla provide record locking when there is simultaneous access to the same bug? Does the second person get a notice that the bug is in use or how are they notified?== | ||
Bugzilla does not lock records. | Bugzilla does not lock records. It provides "mid-air collision" detection, which means that it warns a user when a commit is about to conflict with commits recently made by another user, and offers the second user a choice of options to deal with the conflict. | ||
It provides mid-air collision detection | |||
which means that it warns a user when a commit is about to conflict | |||
with commits recently made by another user, | |||
and offers the second user a choice of options to deal with the conflict. | |||
==Can users be on the system while a backup is in progress?== | ==Can users be on the system while a backup is in progress?== | ||
Yes. You should use the commands included with your database software to run the backups of your Bugzilla data. You can find strategies for dealing with backup considerations at http://www.mysql.com/doc/B/a/Backup.html for MySQL and at http://www.postgresql.org/docs/8.0/static/backup.html for PostgreSQL. | Yes. You should use the commands included with your database software to run the backups of your Bugzilla data. You can find strategies for dealing with backup considerations at http://www.mysql.com/doc/B/a/Backup.html for MySQL and at http://www.postgresql.org/docs/8.0/static/backup.html for PostgreSQL. | ||
==Can I restrict a user's ability to edit certain bug fields?== | |||
Users can only edit bugs if they are the Assignee, the QA Contact, or are in the '''editbugs''' group. (Certain fields can also be edited by the Reporter. Also, all users can ''always'' comment and CC themselves on bugs.) However, note that by default, '''all users are in the editbugs group'''. If you want to change this default, go to Administration -> Groups, choose "editbugs" and clear the "userregexp" field. Then you can use Administration -> Users to explicitly add back certain users into the "editbugs" group, if you want them to be able to edit every field on every bug in the system. (Also, you can use Administration -> Products -> (select product) -> Group Controls to give groups of users "editbugs" for specific products.) | |||
If you want any finer-grained control than that, it requires code changes. You have to edit the <code>check_can_change_field</code> subroutine in the file <tt>Bugzilla/Bug.pm</tt>. The file has many comments to help guide your edits. | |||
==How do I make it so that bugs can have an UNCONFIRMED status?== | ==How do I make it so that bugs can have an UNCONFIRMED status?== | ||
| Line 161: | Line 164: | ||
See [[Bugzilla:Move Installation]]. | See [[Bugzilla:Move Installation]]. | ||
== I restricted a product to be visible to more than one group, and now only users who are members of all of those groups can see it. How do I make it visible to someone who's a member of any of those groups (but not all of them)? == | |||
Bugzilla treats all of the group restrictions on a product as an AND comparison. That is, if you put group controls for more than one group on the same product, then users must be a member of ALL of those groups to be able to perform the restricted action. | |||
If you want OR groups (a member of any of the groups can do it), all is not lost. The way to do this is to create two different sets of groups. | |||
The first set of groups defines groups of people. These groups are not used for group controls on products. In fact, you can leave the "use for bugs" setting turned off on them. These are the groups you will make users be members of. Groupings such as "engineering" or "QA" or "security-team" or "marketing" or similar. | |||
The second set of groups has no users in its membership. You use these groups to define things you want to use group restrictions on, and these will be the groups that you set up in the Group Controls in the product editor. For example, if you have a product (or a set of 3 or 4 products) that you wish to secure to the same set of people, create a group for it. These groups will need to have "use for bugs" checkmarked. Then in the "Groups That Are a Member of This Group" section, add the people groups you created above that you want to be able to access things secured with this group. | |||
=Email= | =Email= | ||
| Line 178: | Line 191: | ||
==Can Bugzilla run on Windows? How?== | ==Can Bugzilla run on Windows? How?== | ||
Yes, Bugzilla can run on Windows. See the [[Bugzilla:Win32Install]] page for information about how to install and configure Bugzilla on Windows. | Yes, Bugzilla can run on Windows. See the [[Bugzilla:Win32Install]] page for information about how to install and configure Bugzilla on 32-bit Windows. See the [[Bugzilla:WindowsServer2008Install]] page for information about how to install on configure Bugzilla on Windows Server 2008 64-bit. | ||
=For Users= | =For Users= | ||
| Line 200: | Line 213: | ||
==How do I search for public bugs (bugs that aren't restricted to a group)?== | ==How do I search for public bugs (bugs that aren't restricted to a group)?== | ||
You can search for bugs without a group by using Boolean Charts at the bottom of the Advanced Search page: "Group" + " | You can search for bugs without a group by using Boolean Charts at the bottom of the Advanced Search page: "Not (negate this whole chart)" + "Group" + "matches regular expression" + "." | ||
= | =Troubleshooting= | ||
== | ==Bugzilla can't connect to the database== | ||
Here's some things to check: | |||
# Make sure that the <tt>$db_user</tt> and <tt>$db_pass</tt> settings in the <tt>localconfig</tt> file are correct. | |||
# If you're using MySQL, make sure that DBD::mysql was compiled against the version of MySQL that you're using. For example, a DBD::mysql compiled against MySQL 4.0 won't work with MySQL 5.1. In versions of Bugzilla 3.2 or greater, you can re-install DBD::mysql by doing: <pre>./install-module.pl DBD::mysql</pre> in your Bugzilla directory. | |||
==I tried to move my Bugzilla from one machine to another, and now there's something wrong with the data.== | |||
and the | |||
Make sure that you followed the instructions on [[Bugzilla:Move Installation]]. In particular, when you import a database dump, your database has to be '''totally empty''', meaning that it must have no tables in it at all. | |||
==I get the error "MySQL server has gone away"== | |||
This usually means that the <tt>max_allowed_packet</tt> setting in your MySQL configuration is too small. It needs to be set larger than the largest piece of data you're trying to insert in to the database. (Usually, this means it has to be larger than your <tt>maxattachmentsize</tt> parameter.) The MySQL configuration is usually in <tt>/etc/my.cnf</tt>. | |||
to your | |||
== | ==I have Apache's mod_security installed, and Bugzilla is not functioning.== | ||
Bugzilla is not compatible with mod_security. You will have to uninstall mod_security or disable it for Bugzilla. | |||
= | ==My parameters don't update when using editparams.cgi, what am I doing wrong?== | ||
Bugzilla's parameters are stored in the <tt>data/params</tt> file. | |||
In order to update parameters, the '''user that your web server runs Bugzilla's scripts as''' needs permission to: | |||
* create, alter and delete files in Bugzilla's <tt>data/</tt> directory | * create, alter and delete files in Bugzilla's <tt>data/</tt> directory | ||
* alter and delete the <tt>params</tt> file in Bugzilla's <tt>data/</tt> directory | * alter and delete the <tt>params</tt> file in Bugzilla's <tt>data/</tt> directory | ||
==Old Charts complain about "Unable to open the chart datafile ./data/mining/-All-"== | |||
==Old | |||
See http://www.bugzilla.org/docs/tip/html/extraconfig.html for | See http://www.bugzilla.org/docs/tip/html/extraconfig.html for information on how to set up the <tt>collectstats.pl</tt> script to enable the Old Charts and New Charts. | ||
==My problem isn't listed here== | ==My problem isn't listed here== | ||
If all else fails, check out places you can get [http://www.bugzilla.org/support/ support for Bugzilla]. | If all else fails, check out places you can get [http://www.bugzilla.org/support/ support for Bugzilla]. | ||
[[category:Bugzilla|F]] | [[category:Bugzilla|F]] | ||