Archive:LegacyBugzilla

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (1 revision(s))
m (Sparks moved page LegacyBugzilla to Archive:LegacyBugzilla)
 

Latest revision as of 15:15, 26 March 2013

Contents

[edit] Bugzilla

Bugzilla is a bug tracking system. The Fedora Legacy Project now uses the Red Hat Bugzilla at http://bugzilla.redhat.com/.

[edit] What do I need to use Bugzilla?

To use Bugzilla, you will need a web browser with cookies enabled. You will also need a Red Hat Bugzilla account. You may apply for a free account by going to https://bugzilla.redhat.com/bugzilla/createaccount.cgi (or by selecting the Account menu item from any bugzilla.redhat.com page).

[edit] How do I login to Bugzilla?

Just go to any bugzilla page which requires a login, and you will be redirected to a login page. Once logged in, you'll be redirected back to your requested page.

[edit] How do I enter a bug ticket?

To enter a bug, go to Fedora Legacy Bug Entry screen at the url https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Legacy -- You may want to bookmark this url if you enter bugs frequently.

From the bug entry screen, select the product release version you want to enter a bug for. If the bug covers multiple releases, then select unspecified, then use the Status Whiteboard to insert a keyword for the releases it covers.

Next, select the Component that is having a problem. Components are based on the source rpm name, which may not be the same as the binary rpm name. To find the name of the source rpm which the binary rpm is derived from, use the following command:

$ rpm -qip <binary rpm name>

Where <binary rpm name> is the short-form name of the binary package the bug report is for (e.g. mozilla, tar, perl, etc). Find the line which contains Source RPM:; this is the name of the component you should choose from the list provided.

If you can not determine the proper component name, choose distribution for the component.

Next you can select the Platform (Architecture) the bug applies to, and the Severity of the bug report.

The Cc: field may optionally be used to add someone to the carbon-copy list for all email related to this bug. As the reporter of the bug, you will automatically be copied on any emails, so you do not need to add yourself here.

In the Summary field, enter a one-line description of the bug. Like an email Subject: field, keep it as short yet still as descriptive and informative as you can.

In the Description field, enter the full description of the bug. Include as much detail as possible here. If possible, and always when addding a PUBLISH or VERIFY vote, GnuPG clear-sign your submission.

You may also link this bug to an external bugzilla entry (for example, if you are reporting a bug in the mozilla package, you could link it to an existing bug in the mozilla bugzilla at https://bugzilla.mozilla.org/) or create attachments to the bug (e.g. patches, data files to reproduce the bug, log file data, etc).

[edit] How do I search for bugs?

You may find all Fedora Legacy Bugs by using the url https://bugzilla.redhat.com/bugzilla/buglist.cgi?product=Fedora+Legacy. (This can be found on the front page of the Fedora Legacy web site).

From the main bugzilla page you can do a Simple Search on keywords or bug numbers.

To perform a more advanced search, go to the bug query page at https://bugzilla.redhat.com/bugzilla/query.cgi (or select Query from the menu near the top any buzilla.redhat.com page).

[edit] Additional Bugzilla Links

For additional information, please check out these links: