Difference between revisions of "Contribute/Bugsquad/Quick Introduction to Bugzilla"

Revision as of 02:42, 16 December 2009

Bugzilla is the bug tracking software the KDE community uses to handle the bug reports of their applications.

Our bugtracker is located at https://bugs.kde.org

Main screen of the bugtracker (default style):

Fields of a bug report

Product: Application or library which is being affected by the bug

Component: Specific component inside the product which is being affected by the bug

Version: Version of the application or library which shows the bug (Note: different products could have different policies about this field: it could represent the last version in which the bug is present, or the first version in which the bug appeared)

Priority: Priority of the bug report. It defaults to "NOR"(normal) and it must not be changed.

Severity: Type of bug:

• "Crash": a bug that causes the application to close itself or freeze/hang
• "Normal": a non-crash bug report (misbehavior)
• "Minor": a non-crash bug which is not really important (a little detail)
• "Wishlist": a feature request

Status: Status of the bug report:

• "UNCONFIRMED": the issue was not confirmed by other bug reporters or developers
• "NEW": the issue was confirmed by other bug reporters or contributors
• "ASSIGNED": a developer/user is working to fix it
• "NEEDSINFO": the issue was closed because it is lacking information
• "RESOLVED": the issue was closed because of different motives:

* "FIXED": the bug was fixed by developers/contributors
* "WORKSFORME": the bug cannot be reproduced and it is considered fixed
* "WONTFIX": the bug is not going to be fixed (developers policy)
* "UPSTREAM/DOWNSTREAM": the bug was not related to KDE (problems related to installation and distributions or to external libraries or plugins)
* "INVALID": the described issue was not a real bug (intended behavior or installation problems)
* "DUPLICATE": the bug was already reported

Votes: Current number of votes the bug report has. Votes can be useful to confirm a bug (status changes from UNCONFIRMED to NEW).

Keywords: Special words which are used to mark special reports, in order to find them easily.

CC List: List of mail addresses (from reporters or contributors) who are tracking the bug report and who are going to get a mail notification about every change on it.

More information about bug report's life cycle and other fields can be found at https://bugs.kde.org/page.cgi?id=fields.html

Common Operations

Get a description of the products and components

You can properly identify each KDE application with its bugzilla product component using this feature: Describe components

Searching bug reports

Simple Search

https://bugs.kde.org/query.cgi?format=specific

[Screenshot]

Advanced Search

https://bugs.kde.org/query.cgi?format=advanced

[Screenshot]

Searching Results

Searching Hints

Adding comments

Adding comments to a bug report

[Screenshot]

Modifying status of a bug report (permissions required)

Modifying some of the fields of a bug report

[Screenshot]

Customizing your bugzilla account

Configure your bugzilla account look and feel

[Screenshot]

General Tips

Foo bar