Feature Overview

The Bugs feature is an indispensable part of software/hardware development and project management. It helps teams identify, record, and track product issues effectively. With systematic bug management, teams can ensure that all discovered issues are handled and resolved in a timely manner, thereby improving product quality and stability.

Sanplex allows teams to record bug details comprehensively, including steps to reproduce, actual results, expected results, severity, impact scope, and attachments (such as screenshots). This enables developers to locate and fix issues quickly. In addition, integration between bug management, test cases, and requirements supports closed-loop handling, improving collaboration efficiency and response speed across the team.

Typical Use Scenarios

• Testers: During project execution, when testers run test cases and discover functional anomalies or performance issues, they submit bugs with detailed observations and expected results to ensure the development team can fix them promptly.
• Developers: When developers discover potential bugs or logic errors during coding, they can log the bug and assign it to the relevant owner for follow-up. For example, if a new feature impacts an existing function, the developer should record and fix the bug quickly to avoid degrading user experience.
• Feedback to Bug: After a product is released, users may report issues through support channels. Support staff can record these reports as bugs in the feedback system so the product and engineering teams can respond quickly. For example, if a user reports a UI rendering issue in a mobile app, support can log it as a bug and assign it to the Product Manager for triage.
• Pre-release Bug Handling: Before releasing a new version, the product and engineering team typically performs comprehensive testing and defect cleanup. Bugs are tracked to ensure high-priority items that impact usability are resolved before release. For example, before shipping a new version, the team ensures all high-priority bugs have been fixed to maintain product stability.
• Data Analysis and Improvement: By analyzing bug data, teams can identify common bug types and high-frequency modules, enabling targeted improvements. For example, if a module shows a high bug rate, the team may refactor or optimize the code to improve overall quality.

Another key responsibility for testers is to submit bugs discovered during testing so developers can resolve them.

In Sanplex, there are two entry points for creating bugs:

1. Execution > Test > Bugs
2. Test > Bugs

1. Submit a Bug

Using Test as an example: in the Test module, click Create Bug to submit a single bug or submit bugs in batch.

图1

For batch submission, use Batch Create Bugs > Multi-item Entry.

图2

Each row is treated as the bug title. After import, you must set other required fields manually.

图3

2. Export Bugs

You can export data from the bug list via Export > Export Data.

图4

You can export all bug records, or select specific bugs in the list and export only those items. Click Settings to configure an export template, select the fields to export, and save the template for quick reuse next time.

图5

3. View Reports

Click Bugs > Reports to view bug statistics and analysis.

图6

On the left side of the Reports page, choose a report type and click Generate Report to view the analysis. Reports are displayed as a pie chart by default. You can also switch to a bar chart or line chart depending on the report content.

图7