Difference between revisions of "Bugzilla"
From GnuCash
(→Using Bugzilla: ObfuscateScript) |
(→Using Bugzilla: Insert section structure, explain how to save uncompressed) |
||
| Line 7: | Line 7: | ||
== Using Bugzilla == | == Using Bugzilla == | ||
| − | There is a specific GnuCash " | + | There is a specific GnuCash "Product" subsection which allows you to specifically search for GnuCash bugs. You can use the following quick links to perform actions on the GnuCash Bugs Database: |
Strongly recommended: | Strongly recommended: | ||
| Line 25: | Line 25: | ||
* [http://bugzilla.gnome.org/enter_bug.cgi?product=GnuCash 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. | * [http://bugzilla.gnome.org/enter_bug.cgi?product=GnuCash 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. | ||
| + | === Attachments === | ||
If a program crash or freeze only happens on a specific file like | If a program crash or freeze only happens on a specific file like | ||
* data file | * data file | ||
| Line 30: | Line 31: | ||
* (modified) report | * (modified) report | ||
it can be useful to attach a ''copy'' of that file to your bug report, but: | 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''. It can then already be seen in the web interface. | + | * It is easier, if you attach your XML data file ''uncompressed''. Before you save your file, uncheck <tt>Edit->Preferences->General->Files->Compress Files</tt>. 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 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. | * If the file is really big, try to create a minimal example. | ||
| Line 37: | Line 38: | ||
* most import files are of type ''text/plain''. | * most import files are of type ''text/plain''. | ||
| + | === Answer === | ||
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. | 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 == | == Bug Triage == | ||
For people, which like to help us e.g. on bug triage, are some additional informations in [[QA/BugzillaAdministration]]. | For people, which like to help us e.g. on bug triage, are some additional informations in [[QA/BugzillaAdministration]]. | ||
Revision as of 13:57, 20 February 2015
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 - use their Request Tracker at the Comprehensive Perl Archive Network (CPAN).
Using Bugzilla
There is a specific GnuCash "Product" subsection which allows you to specifically search for GnuCash bugs. You can use the following quick links to perform actions on the GnuCash Bugs Database:
Strongly recommended:
Other links into bugzilla:
- Search the entire GNOME bug database
- Search for open GnuCash bugs and enhancements
- Search for open GnuCash bugs and enhancements, restricted to post-1.8 or unspecified versions
- 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.
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 are of type text/plain.
Answer
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 people, which like to help us e.g. on bug triage, are some additional informations in QA/BugzillaAdministration.
