In addition to completing tasks, a developer's primary responsibility is confirming and resolving bugs.

Once a build is submitted for test and the testing phase begins, bugs will inevitably arise. Resolving these bugs is a critical duty of the development team.

Sanplex features a streamlined bug-handling workflow. A standard lifecycle follows this path: Tester submits a Bug => Developer confirms/resolves the Bug => Tester verifies and closes the Bug.

Alternatively, if a fix fails verification, the activation workflow applies: Tester submits a Bug => Developer resolves the Bug => Tester fails verification => Bug is Activated => Resolved again => Verified and Closed.

Developers are responsible for confirming and resolving bugs assigned to them and recording the specific solution within Sanplex.

How do developers confirm and resolve bugs in Sanplex? Check out the video explanation:

【视频介绍】

I. Confirming a Bug

If a developer cannot resolve a bug immediately after it is submitted, they can use the Confirm action to provide feedback to the tester.

• The Bug list indicates whether a bug has been confirmed.
• The Confirm button is available on both the Bug details page and the right-hand action bar of the Bug list.
• Note: Once a bug is resolved, its status automatically changes to "Confirmed."

Developers can confirm bugs directly via Dashboard > To-Do > Bug, Test > Bug, Project > Test > Bug, or Execution > Test > Bug.

The Confirm button in the Test > Bug list:

图1

II. Resolving a Bug

Developers can click the Resolve button on the Bug details page or within the Bug lists in the Dashboard, Test, Project, or Execution modules.

图2

The Resolve button on the Bug details page:

图3

After clicking Resolve, you must select a Resolution and a Resolved Build.

图4

Once successfully resolved, the bug status changes from "Active" to "Resolved."

III. Bug Resolutions Explained

1. Standard Resolutions in Sanplex

Sanplex provides seven default resolutions:

• By Design: The behavior is intended; no changes are needed.
• Duplicate: This bug has already been reported elsewhere.
• External: The issue is caused by external factors outside the system.
• Fixed: The bug has been successfully resolved.
• Not Repro: The bug cannot be reproduced.
• Postponed: It is a valid bug, but it will be handled at a later date.
• Will Not Fix: A decision has been made not to resolve the issue.

Special Note : Bugs marked as "Fixed" or "Postponed" are considered valid bugs. To add custom resolutions, navigate to Admin > Custom > Bug > Resolution.

2. Converting Bugs to Stories

When a bug is converted to a story, the bug is automatically closed. Future tracking of that issue is handled through the story page. Technically, a bug converted to a story is not yet "resolved"; it is simply transitioned into a story for subsequent development.

The To Story button on the Bug details page allows for direct conversion.

图5

• Audit Trail: Information regarding the conversion is logged in the bug's history, story source, and related info sections.
• Auto-Closure: Once converted, the bug is closed with the reason "To Story."
• Navigation: You can click the resulting story name from the bug page to view its details.

A bug automatically closed after successful conversion to a story:

图6