This document describes the "Bugs" feature in classic project management.
Open Project
1. Log in to the CODING Console and click Use Now to go to CODING page.
2. Click
in the upper-right corner to open the project list page and click a project icon to open the project.
3. In the menu on the left, click Project Collaboration.
Feature Overview
In CODING Project Collaboration, the Bugs feature allows a team to keep track of bug information and improve the bug transition and processing efficiency, making large-scale bug management much easier for enterprise users.
1. Open a project and select Project Collaboration > Bugs. Click Create Bug in the upper-right corner of the module and enter a bug title, bug description, and other basic information to create the bug.
2. After creation, the bug is in a To be processed status by default. On the Bug Details page, you can switch the status, set the assignee, associate a parent requirement, plan its iteration, edit the priority, set the start date, estimate or log time, and add tags.
In a bug, you can configure an existing issue as a pre-issue or post-issue with a block dependency. On the Bug Details page, select Block Relationship on the top, search for an issue by its ID or title, and then associate it. You can switch between pre-issues and post-issues. For more information, see Block Dependency.
In the Description or Comments on the Bug Details page, you can use # + ID/title to reference 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 # + ID/title to reference 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 organize and track bugs and implement bug processing workflows. Bug statuses include "To be processed", "In progress", "To be verified", "Rejected", "Reopened" and "Closed".
1. After creating a bug on the bug list page, go to the bug details page. The bug status is To be processed by default. Select options from the dropdown menu on the right to switch its status.
2. On the bug list page, you can switch the status based on the current stage of the bug in the Status column.
3. Click Project Settings > Project Collaboration > Issue Types > Bugs, and then select Workflows to set custom bug workflows. For more information, see Custom Workflows.
On the bug list page, you can switch between Tile View and Kanban View in the upper-right corner to suit your needs. The next time you go to this page, the system will display the last used view by default. You can use the search bar with filters to quickly find the content you want. For more information, see Manage Issue Views.
Changes and modifications to a bug are recorded in the action log. View the version to view all earlier versions. Version backtracking allows you to restore an earlier version. For more information, see Version Management.
When creating and managing a bug, you can set the bug type.
Note:
CODING Bug Management provides five bug types by default:
Functional bug
UI defect
Usability defect
Security defect
Performance defect
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.
Yes
No
Was this page helpful?