Creating Bugs

You can create a bug to trace the problems found in the test and verification phase of software features and functions.

Prerequisites

An IPD-standalone software project is available, in which you have permission to create and duplicate bugs.

Creating a Bug

Access the CodeArts Req homepage.
On the project homepage, choose Defects.

Click Bug. On the Bug page, set related parameters.

**Table 1** Creating a bug
Parameter	Description
Title	Title of a work item.
Description	Enter the fault symptom description, environment information, onsite fault locating developers, and the preliminary cause determined by developers based on site requirements. Use text, 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	Owner of the bug. Select one or more members of the responsible 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. After a module is created, you can edit and delete the module, and add child modules.
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 the 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.
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.
Expected Rectification	Planned rectification time.

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 Notifications.

Related Operations

You can perform the following operations on a new bug.

**Table 2** Basic operations on a bug
Operation	Description
Modify bug title	Click next to a bug title to modify it.
Modify bug field	Click the target field value in the row of a bug to modify the value.
Duplicate bug	Click in the Operation column. This process is the same as that of creating a new bug.
Migrate bug	Click in the Operation column of a bug to migrate it to other projects. NOTE: Bugs in a Done state cannot be migrated. After migration, The bug will be handled again. The actual workload, related items, tags, discovering PI, and fixing PI of the bug will be cleared. Only the custom bug fields of the target project will be displayed.
Collaborate on bug	Click in the Operation column of a bug to assign it to other projects under your tenant.
Delete bug	Choose > Delete in the Operation column of a bug to delete it. NOTE: Bugs that are being reviewed or in a Doing state cannot be deleted. If you delete drafted bugs, they are permanently deleted. Bugs in a To Do state can be deleted only in the proposing project. Bugs in a Done state can be deleted in both the proposing project and the responsible project. If you delete bugs of the proposing project, they are permanently deleted. If you delete bugs in the responsible project, they are moved to the project's recycle bin. Bugs in the recycle bin can be restored or permanently deleted. After being restored, bugs restore to their original status.