Managing Bugs

Search for bug

• By adding filters
  1. Click the search box in the bug list and select one or more filters to search for bugs.
  2. To clear all filters and display all data, click on the right of the search bar.
• By using a saved view
  1. Click the search box in the bug list and select one or more filters.
  2. Click on the rightmost of the search bar, and enter a view name.
  3. Click OK. The created view is displayed next to the Bug button.
  4. Select the created view to query the bugs that meet the search criteria.

     Views can be shared with others, modified, and deleted.

Import work items

Use a template to import bugs in batches.

1. In the bug list, click on the right of the search bar and select Import.
2. In the displayed dialog box, click Download Template.

   The template file should be named in the following format: Project name + "-" + Module name (for example, Bug) + Template. You can edit the name of the downloaded template.

3. Set the fields in the Bug Import sheet of the template.

   For details about how to set parameters, see the Notes and header instructions in the template file.

4. Drag and drop the desired file to the import area or click the import area and select the file.
5. Click Next. The verification progress dialog box is displayed.

   After the verification progress reaches 100%, close the dialog box and view the verification result. If the mandatory fields fail the verification, the import is not allowed, while the verification result of optional fields does not affect the import.

   • If the verification is successful, click Confirm Import.
   • If the verification fails, modify the file based on the verification result. Click Last step to import the modified file.
6. After the verification is successful, click Confirm Import. The import progress dialog box is displayed. You can click Check progress in the dialog box to go to the Import/Export Records page to view the import records.
7. After the import is successful, view the imported information in the bug list.
   • If the import fails, a message is displayed on the page. Click View Failure Details in the message to view the failure details. You can modify the requirement information based on the details and import the template file again.

Export work items

Export bugs in batches to an Excel file.

1. Export some or all bugs.
   • Export all: On the Defects page, click on the right of the search bar and choose Export. The Select Fields to Export dialog box is displayed.
   • Export some: In the bug list, select one or more bugs to be exported and click Export Selected at the bottom of the page. The Select Fields to Export dialog box is displayed.
2. Select the fields to be exported.
3. Click Export. A dialog box is displayed, indicating the export progress.
   • After the bugs are exported, click Download. The bug file will be downloaded to the local PC. The file format is .xlsx.

Configure fields to display

Clone bugs across projects

Constraints

• Only bugs of the current project can be cloned to other projects. The workload, associated work item, tag, and release sprint fields will be cleared.
• You must have permission to create and clone bugs for the target project.
• Bugs can be cloned only to projects of the same type.
• You can clone up to 50 tasks at a time.
• Draft bugs and bugs of other projects cannot be cloned.

Procedure

1. Select the bug to clone in the bug list and click Cross-Project Copy in the lower part of the page. The Cross-Project Copy window is displayed.
2. Select a target project from the drop-down list. You can select only a project to which you have joined and must have permission to create and clone tasks for the target project.
3. Click Next. The window for setting mandatory fields is displayed. Select the target owner from the drop-down list (the current operator is selected by default). Mandatory fields are those on the bug creation page of the target project.
4. Click OK. The bugs are cloned to the target project.
5. Go to the target project to view the cloned bugs.

Transition statuses in batches

Constraints

• Only bugs of this project support batch status transition.
• The selected bugs must be in the same status.
• You must have permission to set statuses for bugs.
• All mandatory fields of the selected bugs have been set.

Procedure

1. Select the target bugs in the bug list and click Batch Transfer in the lower part of the page. The Batch Transfer window is displayed.
2. Select the target status from the drop-down list.
3. Click Next.
4. Set mandatory fields. The mandatory fields are set on the In-transition GUI Config tab page of the project's bug status flow configuration page.
5. Click OK.

Perform batch operations

You can select multiple bugs to perform operations in batches: edit, suspend/unsuspend, export, delete, cross-project clone, and transition.

Group bugs

You can group work items by any supported field type.

• For bugs of other projects and projects in a program (after sub-project aggregation is enabled), grouping by release, sprint, module, feature set, or tag is unavailable.

Procedure

1. On the Bugs page, click Group.
2. On the displayed page, select the fields used to group work items.
   • You can sort work items in ascending or descending order.
   • You can enter a keyword to search for fields.
   • When work items are grouped by multi-select list or multi-select user, the same work item may appear in multiple groups.
   • You can click No grouping to ungroup work items.

Version snapshots

Snapshots include plan management snapshots, feature tree snapshots, and work item snapshots. A version snapshot is a work item snapshot. Its name is automatically generated by the system.

Constraints

A work item can have a maximum of 1,000 snapshots.

Procedure

1. In the bug list, select the work items for which you want to create a snapshot.
2. Click in the lower part of the page to take a snapshot of the selected work items. A message is displayed in the upper right corner of the page, indicating that the operation is successful. The snapshot is a work item snapshot. Its name is automatically generated by the system.

   The format of the work item snapshot name is: Work item type + "v" + Year + "." + Month + "." + Day + "." + Number of versions generated on the current day.

   For example, if a bug is snapshotted for the first time on March 25, 2026, its snapshot name generated by the system is Bug v26.03.25.1.

   NOTE:

   You can also go to the work item details page, click in the upper right corner, and select Version Snapshot to create a snapshot for the work item.

3. (Optional) Click the work item name to go to its details page, click , and select Version History to view the generated snapshots.

Edit work item

On the bug details page, click the value box of the field to be modified, and enter a target value in the text box or select one from the drop-down list. The modification is saved automatically.

You must have permission to edit bugs.

Change work item status

Go to the work item details page, click the Status field, and transition the work item to the target status. For details about status transition, see Table 1.

You must have permission to update statuses for bugs.

Upload attachment

Attachments can be pictures, workbooks, manuscripts, and text files. A maximum of 100 attachments can be added to each work item, and their total size cannot exceed 500 MB.

1. Go to the work item details page, and click the Attachment tab.
2. Click the box to select a local file or drag the file here to upload it as an attachment for the work item.

   Local files can be directly dragged to the text box. When the upload progress reaches 100%, the system displays a message indicating that the attachment is uploaded successfully.

   Move the cursor to the file that is successfully uploaded. The operations that can be performed are displayed.

   • Click to download the file.
   • Click to delete the uploaded file.

You must have permission to edit or upload attachments for bugs.

Add and check related item

A work item can be associated with other types of work items in a project.

1. Go to the work item details page and click the Related Items tab.
2. Complete association.
   • Associate Work Item: Associate work items of any type in the project.

     To associate existing RRs, create an RR first.

     To associate existing IRs, SRs, and ARs, create and break down an R&D requirement first.

     To associate existing tasks, create a task first. To cancel the association, click .

     To associate existing bugs, create a bug first. To cancel the association, click .

   • Associated upstream bugs: bugs coordinated from upstream projects.

     The upstream bug information is displayed only when their responsible project is set to the current project on their downstream bug association page.

   • Associated downstream bugs: bugs assigned to other projects for collaboration.

     A maximum of 10 child bugs can be created at a time. One child bug is displayed by default and cannot be deleted.

     1. Click Assign Owner.

     2. Configure the information about bug assignment. Click to expand and configure more information.

     3. Click OK. The bug is assigned. The bug can only be viewed and handled in the responsible project.

     After a bug is assigned for collaboration, its attachments will not be synchronized to the downstream bugs. The current owners of these downstream bugs can contact the bug creator to obtain attachments.

   • Associated open issue review form: reviews that include the review and approval comments related to the work item.
   • Test Plan: test plans related to the current bug. You can associate test plans with the current bug.
   • Test Case: test cases related to the current bug. You can associate bugs with test cases in CodeArts TestPlan. The associated cases will be displayed here.
   • Code Commit Record: code submission records related to the current bug.

     Related information is displayed only when the current bug is associated during code commit.

   • Code Merge & Change Request: code merge and change requests corresponding to a bug.

     Related information is displayed only when a submitted merge or change request is associated with the current bug.

   • Code Branch: code branches related to the current bug.

     Related information is displayed only when a code branch is associated with the current bug.

   • External Link: External links associated with the current work item.
     • Add Link: Click "Add Link", fill in "Link Name" and "Link" in the pop-up window, where "Link" must start with "https://" and cannot contain invalid characters. Invalid characters refer to spaces, Chinese characters, or other characters that cause the URL to be invalid. After setting, click "OK" to complete the creation of the link. After completing the settings, click "OK" to finish creating the new link.

       After a new link is successfully created, click "External Link" to view, edit, copy, or delete the link.

       

     • Copy a link: Click on the right of the link to be copied.
     • Edit a link: Click on the right of the row where the link to edit is located. In the displayed dialog box, you can change the link name and link.
     • Delete a link: Click on the right of the link to be deleted. In the displayed dialog box, click Delete.

You must have permission to associate/dissociate work items, assign bugs, associate/dissociate files, and associate/dissociate wikis for bugs.

Add workload

1. Go to the work item details page and click the Workload tab.
2. Click Add Workload. The Add Workload dialog box is displayed.
3. Enter the workload information.
   • The end date cannot be earlier than the start date.
   • Decide whether to select Weekends included. If not, weekend workload records will not be generated.
   • You can select Total or Daily for Workload.
   • Work Type options include backend development, frontend development, UI design, replacement leave, debugging, and general. You can also customize the value by referring to Creating Work Types.
4. Click OK.

   The system automatically generates corresponding records based on the entered dates and days.

   The workload can be edited and deleted.

You must have permission to add person-hours for bugs.

Workloads can be edited and deleted by the creator. By default, the project administrator can edit and delete all workloads.

View operation history

History displays all operation logs of users, including creation, status transition, review initiation, work item association, and workload addition.

1. Go to the work item details page.
2. Click the History tab.
   • Click or to check historical records in the ascending or descending order of operation time.
   • You can set search criteria to query historical records that meet the search criteria.

You must have permission to view bugs.

Tag work item

1. Go to the work item details page. Click next to Tag at the top of the page, and select Create Tag.

   The added tag is displayed in the Tag area.

2. In the Create Tag dialog box, set Tag Name and select Tag Color.
3. Click OK.

   The new tag is displayed next to the bug ID in the bug list.

4. (Optional) Hide a tag.
   • Click next to Tag. In the displayed dialog box, deselect √ to hide the tag.
   • Move the cursor to the tag name and click to hide the tag.
     Figure 2 Hiding a tag - 02
     
     NOTE:

     To add or remove tags for multiple work items, select the desired work items, click Batch Edit in the lower part of the page, and select Tag.

You must have permission to edit bugs.

Add comment

1. Go to the work item details page.
2. On the Details tab page, click the Comments text box.
   Figure 3 Add comment
   
3. Enter a comment.

   You can upload images, enter links, associate work items, and use @ to notify project members in comments.

4. Click Submit.

   Submitted comments can be replied, edited, pinned to the top, and deleted.

You must have permission to view bugs.

History versions

For work items with snapshots, you can view their historical versions and compare the differences between them.

1. Go to the work item details page, click in the upper right corner, and select Version History.
2. In the Version History dialog box, select two versions and click Compare Versions. On the Work Item Version Comparison page, view the differences between the original version and the compared version. You can click in the upper right corner and enable Hide Identical Items to view only the differences between the two versions.
3. On the Work Item Version Comparison page, click to return to the Version History page. Hover over a snapshot version. is displayed. Click to delete the snapshot.
   NOTE:

   If a work item has a third-party snapshot or its child work items have third-party snapshots and the child work items cannot be separated from the current work item, the snapshot cannot be deleted.

You must have permission to view bugs.

To delete a snapshot, you must have permission to delete bugs.