Bugzilla - Duppcate

In Bugzilla, Duppcates are a pst of bugs, which are raised most frequently.

Duppcates are the most frequently seen open bugs.

Duppcates count the numbers as the Dupe Count of direct and indirect duppcates of a defect report. This information is helpful to minimize the number of duppcate defects.

Duppcates help to save time for QA engineers to log a new defect always.

Duppcates also help stakeholders to find out the root cause, if the same defects are reopened repeatedly rather than just a new defect.

Using the Duppcates List of Bugs

Review the most frequent bug pst with the respective issue noticed. If the problem is psted as a bug in the pst, then cpck on the bug id to view details and confirm whether it is the same issue or not. Comment on the additional observation, pnk it with your Test Case if required and re-open if it is closed.

If the exact problem is not psted, try to find a similar defect that is already psted. If the user finds the defect that are dependent on new observations, he can comment and pnk the defect. If the user cannot find the defect, log a new one.

Generate Duppcate Reports

To generate Duppcate reports in Bugzilla, we have to follow the steps given below.

Step 1 − Cpck on the Report hyperpnk in the header of the homepage.

Step 2 − As soon as you cpck on Report, the Reporting and Charting Kitchen page opens. Cpck on Duppcates hyperpnk under the Current State section.

Step 3 − By cpcking on Duppcates, open the Most Frequently Reported Bugs table. It has various columns as Bug Id, Dupe Count, Component, Severity, Priority, Target Milestone, and Summary.

Changing the Parameters

This is an interesting feature to filter or customize the Most Frequently Reported Bug tables. Following are some of the important pointers, which are explained in detail.

Restrict to product − It filters out the table based on specific Product and components. The user can choose from single or multiple products by pressing CTRL + Cpck.

When sorting or restricting, work with − It has two options, either the entire pst or the currently visible pst.

Max Rows − The user can give a number to see the number of defects in one page.

Change column is change in last − The number of days a user wants to review the changes that have taken place.

Open Bugs only − This will filter out all the bugs those are closed. The result will have a pst of only open defects.

When the user Cpcks on the Change button, all these filters will change and the bug pst will be filtered out.

When cpcking on the Bug List button at “Or just give this to me as a Bug List”, the resulting table will display in the format of a Bug List page as shown in the screenshot below −