The Known Bugs List and the ❝Similar Issues❞ feature help identify and avoid documenting previously reported bugs, making it easier and faster to report new ones. By leveraging the information already available, you can save time and resources and focus on finding new bugs rather than duplicating effort in reporting already known ones.
The Known Bugs List
One of the primary functions of the Known Bugs List is to prevent the submission of duplicate bug reports. Customers can add bug reports to this list, making them visible during test cycles. This feature helps testers avoid repeatedly submitting the same issues or those with similar underlying root causes.
If the customer has marked a bug as known, the Known Bugs tab will be shown, and you'll see the list of bug reports with the status: ❝Accepted by customer❞.
Before you submit a bug report, you'll need to look at the Known Bugs List. If you cannot find any bugs or discover that other testers have already reported the ones you encountered, it's time to submit reproductions instead. This ensures that the focus remains on identifying unique issues.
Suppose your bug report is rejected with the rejection reason ❝Known bug❞. In that case, the bug was already submitted in a previous test cycle and added to the Known Bugs List because customers are primarily interested in unique bugs that our testers have not reported in prior cycles. So, double-check the Known Bugs List to save time and effort!
The "Similar Issues" Feature
In addition to the Known Bugs List, another powerful tool at your disposal is the ❝Similar Issues❞ feature. This feature enhances your bug-reporting experience by helping you efficiently identify duplicates and known bugs.
When viewing a bug report, the system may present you with one or more similar bug reports under the ❝Similar Issues❞ headline on the right-hand side. These bugs are from the same test or the Known Bugs List, helping you spot duplicates and save valuable time.
Take the time to go through all the reports listed under ❝Similar Issues❞. This step is essential to accurately judge the current bug report and determine if it's a unique issue.
As you input text into the bug report form, upon selecting the feature and bug type (and severity if it's a functional bug), the system will display similar bug matches on the right navigation bar above the feature description. This feature remains accessible regardless of the language you use to submit your report, and you also have the Check for similar button at the bottom.
If you find that the bug you're reporting is displayed in the ❝Similar Issues❞ section on the right-hand side, it means the issue has already been reported. In such cases, you can click the reproduction button next to it; there's no need to file a redundant report.
To streamline your bug reporting process, consider these pro tips:
- Use the Known Bugs tab to search by keywords, to filter features and bug types.
- Review attachments and descriptions in original bug reports.
- Check the ❝Similar Issues❞ section in the right sidebar while submitting your report.
In conclusion, efficient bug reporting is essential for a streamlined testing process. The Known Bugs List and ❝Similar Issues❞ feature are potent tools that can help testers avoid duplication, identify known issues, and ensure that unique bugs receive the attention they deserve. Incorporating these features into your bug-reporting workflow can improve your tester's quality and testing time efficiency.