This document describes bugs in Scrum agile management.
A bug is a failure to meet an initially defined business requirement. Bugs include any such defect except coding errors.
On the CODING platform, you can centrally manage bugs. By recording detailed bug information such as the bug type, assignee, iteration, priority, and module, test engineers can learn about the overall bug handling progress, thereby improving bug transitioning and handling efficiency.
Open a project and select Project Collaboration > Bugs. Click Create Bug in the upper-right corner and enter a bug title, bug description, and other basic information to quickly create the bug.
You can create sub-issues under a bug to break down a large bug.
···to the right of a sub-issue and change the associated parent issue or delete the current sub-issue.
···in the upper-right corner, and then convert the bug to a new requirement or change its parent epic.
After creating a bug and breaking it down into sub-issues, you can enter the details page to set the iteration and associated requirements, set the story points, select the bug type, adjust the priority, set the due date, and specify the assignee.
In the Description or Comments on the bug details page, you can use
# + reference ID/title to select a resource. The resource referenced will be shown in the References list. If the current bug has been referenced by another resource, the resource will be shown in the Referenced By list of the bug.
You can also associate a code commit with an issue. When committing code, add the
# + reference ID/title of the issue to the commit information (for example, this is a commit #3). See Reference Resources and Upload Attachments for details.
Bug status refers to the stage of a bug in its lifecycle and provides a way to implement bug processing workflows.
The bug list is a list view of all bugs in the project. It is the main workspace for testers and relevant bug assignees. On the bug list page, you can switch between ** Tree View**, Tile View, and Kanban View to suit your needs. The next time you go to this page, the system will display the last used view by default.
When there are many tasks, flexibly use the search box and filters to quickly locate the information you need. For more information, see Manage Issue Views.
All changes to a bug are recorded in the action log. On the details page, select
··· in the upper-right corner and click Earlier Versions in the menu to view all versions by time. Version backtracking allows you to restore an earlier version. For more information, see Version Management.
You can batch import and export bugs. On the bug list page, select
··· in the upper-right corner and import or export bugs. For more information, see Import and Export Issues.
When creating and managing a bug, you can set the bug type. CODING Bug Management provides five bug types by default:
Custom bug types are also supported. Only a team owner or admin can create bug types. After a bug type is added, the bug type can be used for all projects of a team.
This feature is used to configure modules to which the bugs belong. Creating different modules allows you to manage and locate bugs easily to suit the needs of professional scenarios. Module data can be shared across projects for more efficient collaboration.
On the bug details page, you can select
··· in the upper-right corner and click Delete in the menu. Deleting a bug will delete all its sub-issues as well. Proceed with caution.