Creating Bugs

Prerequisites

A project has been created.

Procedure

1. On the project homepage, choose Bugs.
2. Click Create Bug.
3. Enter the basic information about the bug.

   Parameter	Description
   Tag	When creating or editing a work item, you can add a customized tag. Tag name can be marked in different colors.
   Title	Title of a work item.
   Description	Enter the fault symptom description, environment information, onsite fault locating R&D personnel, and the preliminary cause located by the R&D personnel based on the site requirements. The description can include texts, images, or links.
   Attachment	A maximum of 100 attachments can be added to a bug, and the total capacity is 50 MB.
   Proposed Project	Project to which the bug creator belongs, which cannot be changed.
   Responsible Project	Project to which a bug belongs.
   Raised By	Test personnel who find the bug.
   Owner	The default value is the test manager of the project to which the bug belongs. If the project does not have a test manager, you can select the administrator or manager of this project.
   Module	Module to which a bug belongs. The module value can be customized as follows: Click . The Modules dialog box is displayed. Click Create. Set Module, Description, and Owner. The value of Module must be unique. Click OK. The module is created. After a module is created, you can edit and delete the module, and add submodules.
   Severity	Severity of a bug. The options are Info, Minor, Major, and Critical.
   Responsible Release	Release plan where a bug is found. This parameter has a value only after operations in Creating Release and Sprint Plans are completed. The parameter value can be empty. You can create a release and then associate it with the release.
   Responsible Sprint	The next level of the release. This parameter has a value only after operations in Creating Release and Sprint Plans are completed. The parameter value can be empty. You can create a sprint and then associate it with the sprint.
   Environment	Environment where a bug is found. The options are development self-test environment, test environment, and production environment.
   Copy To	Other members in the project. The selected members will receive a system notification. Project member information can be added. For details, see Managing Members.
   Expected Rectification	Planned rectification time.

4. Click Submit. The Bugs tab page is displayed, and a message is displayed in the upper right corner, indicating that the bug is created successfully.

   The new bug is displayed in the bug list, and the state is Analyzing.

   

   After a bug is created, the people selected for Owner, Raised By, and Copy To will receive email notifications and internal message notifications. If not, set notifications or modify notification settings. For details, see Configuring Notification Settings.

More Operations

After creating a bug ticket, you can perform the following operations as required:

• To duplicate a bug, click in the row where the bug to be copied is located.

  You can select Responsible Project for the bug to be duplicated. If the selected responsible project is not the current project, view the bug in the responsible project.

• To filter the fields displayed in the bug list, click next to the Operation field, and set the fields to be displayed in the task list.
  • On the left of the pop-up box, select the fields to be displayed in Available.
  • On the right of the pop-up box, drag the fields in Selected to adjust the display sequence.