Difference between revisions of "Bugzilla"

Revision as of 23:28, 17 March 2017

Bugzilla is a repository of bugs and enhancement requests maintained by the Gnome Project and used by the GnuCash project.

Other Resources

• Also, uservoice.com is an interesting forum for discussion of new feature requests (but not bug reports).
• If Finance::Quote is not working correctly, you can test it by using the gnc-fq-* command line tools, see FAQ. Use their Request Tracker at the Comprehensive Perl Archive Network (CPAN).

Using Bugzilla

There is a specific GnuCash "Product" page which inter alia allows you to specifically search for GnuCash bugs. E.g. can you there click number right of the interesting component and will get the list of the open bugs.

Bug Mail

If you want to receive email notifications about a particular bug, you can add the email address that is your Bugzilla id to the CC list on the bug. Bugzilla will do this for you by default if you take any action on the bug page. If you want to be notified about all changes to particular categories of bugs, including new ones, add one or more of the following email addresses to your "User Watch" list in Bugzilla Email Preferences: Click the Preferences item in the Bugzilla menu bar and select the Email Preferences tab. The watch list is underneath the table with all of the check boxes. The email addresses and the groups they monitor are:

Triage

At first you should check for existing reports of the same problem or improvement suggestion. It may be still open or already closed after the date of your release.

Example links into GnuCash's bugzilla section:

• Search the entire GNOME bug database (overwhelming)
• Search for open GnuCash bugs and enhancements
• Search for open GnuCash bugs and enhancements, restricted to post-1.8 or unspecified versions

Entering of or commenting on bugs

You might probably read the FAQ section about bug reporting before you continue ...

Also bugzillas help has useful parts.

• Open a new GnuCash bug or enhancement Request; when reporting a crash, see Stack Trace and Tracefile for information on how to produce a stack trace for your bug report.

Tip

If you refer to other bugs in your text, we suggest to use the form bug nnnnnn - Title. Bugzilla will then add a link and the reader saves time if the title can be read without following the link.

Do not copy and paste log files. Instead append them as:

Attachments

If a program crash or freeze only happens on a specific file like

• data file
• import file
• (modified) report

it can be useful to attach a copy of that file to your bug report, but:

• It is easier, if you attach your XML data file uncompressed. Before you save your file, uncheck Edit->Preferences->General->Files->Compress Files. It can then already be seen in the web interface.
• If the file contains confidential data do not forget to anonymize your data e.g. with the ObfuscateScript.
• If the file is really big, try to create a minimal example.

When uploading adjust the mime type of your file:

• Uncompressed gnucash data files are of type text/xml,
• most import files and log files are of type text/plain.

Answers

If a developer asked you for some information or one of the files above and you attached them, do not forget, to reset the bug status from needinfo to unconfirmed again.

Bug Triage

For those people who may like to help us e.g. on bug triage, there is some additional information in QA/BugzillaAdministration.