- What's New
- Function Overview
-
Service Overview
- What Is CodeArts Req?
- Advantages
- Use Cases
-
Features
- Multiple Built-in IPD Requirement Models
- E2E Traceability
- Baseline Management and Change Review
- Efficient Cross-Project Requirement Collaboration
- System Feature Management
- Customers' Raw Requirements Management
- Bug Full Lifecycle Management
- Efficient Cross-Organization Collaboration for Bug Tracking and Management
- Bug Trend Analysis and Quality Measurement
- Traceable Fixing Process
- Customizable Fixing Process
- Security
- Permission Management
- Constraints
- Basic Concepts
- Getting Started
-
User Guide
- CodeArts Req Usage Process
- Purchasing and Authorizing CodeArts Req
- Accessing the CodeArts Req Homepage
- Managing a Program
- Creating a CodeArts Project
-
Managing Scrum Project Requirements
- Requirement Management Process
-
Configuring Common Settings
- Configuring Common Work Item Fields
- Configuring Common Work Item Statuses
- Configuring Work Item Fields and Templates
- Managing Work Item Statuses and Transitions
- Configuring Work Item Status Rollup Rules
- Adding Work Item Modules
- Adding Work Item Domains
- Adding Work Types
- Configuring Notification Rules
- Creating and Managing Work Items
- Configuring a Sprint Plan
- Tracking the Project Progress
-
Managing IPD-System Device Project Requirements
- Requirement Management Process
-
Configuring Common Settings
- Configuring Common Work Item Fields
- Configuring Common Work Item Statuses
- Configuring Work Item Templates
- Configuring Work Item Status Flows
- Configuring Work Item Tags
- Creating Work Item Modules
- Creating Work Types
- Configuring Work Item Status Rollup Rules
- Configuring Notification Rules
- Configuring Reviews
- Viewing Work Item Import/Export Records
- Creating and Managing RRs
- Creating and Managing a Feature Tree and System Features
- Configuring Project Plans
- Creating and Managing R&D Requirements
- Creating and Managing Tasks
- Creating and Managing Bugs
- Reviewing Work Items
- Tracking the Project Progress
-
Managing IPD-Standalone Software Project Requirements
- Requirement Management Process
-
Common Configuration Management
- Configuring Common Work Item Fields
- Configuring Common Work Item Statuses
- Configuring Work Item Templates
- Configuring Work Item Status Flows
- Configuring Work Item Tags
- Creating Work Item Modules
- Creating Work Types
- Configuring Automatic Rollup Rules
- Configuring Notifications
- Configuring Reviews
- Viewing Work Item Import/Export Records
- Creating and Managing RRs
- Creating and Managing a Feature Tree and System Features
- Configuring a Plan
- Creating and Managing R&D Requirements
- Creating and Managing Tasks
- Creating and Managing Bugs
- Reviewing Work Items
- Tracking the Project Progress
- (Optional) Checking Audit Logs
-
Best Practices
- CodeArts Req Best Practices
- Best Practices of Scrum Projects
- Using IPD-System Device Projects to Manage RRs of a Smart Watch R&D Project
- Using IPD-System Device Projects to Manage Defects of a Smart Watch R&D Project
- Using IPD-System Device Projects to Perform a Baseline Review (BR) on a Smart Watch R&D Project
- Using IPD-System Device Projects to Manage Feature Trees of a Smart Watch R&D Project
- Huawei E2E DevOps Practice: Managing Requirements
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
- User Information
- Project members
- Project Information
- Project Indicators
- Project Statistics
-
Work Items of the Scrum Project
- Creating a Customized Field for a Work Item Type
- Uploading an image
- Obtaining Work Item Completion Rate
- Obtaining Comments on a Specified Work Item
- Querying Labor Hours by User (Single Project)
- Querying Labor Hours by User (Multi-Project)
- Obtaining the Work Item History
- Create work items.
- Querying Work Items of a Project
- Advanced Query Work Item
- Deleting Work Items in Batches
- Querying Work Item Details
- Updating a Work Item
- Deleting a Work Item
- Obtains sub-work items.
- Querying Historical Records of All Work Items in a Project
- Querying the Work Item Transfer Configuration of a Scrum Project
- Creating a Work Item as a Fine-grained Permission User
- Queries the work items associated with the current work item.
- Queries the associated Wikis associated with the current work item.
- Queries the code submission records or branch creation records associated with the current work item.
- Querying Associated Wikis
- Querying Customized Fields of Scrum Work Items
- Downloading an Image
- Uploading an Attachment to a Work Item
- Iteration of the Scrum Project
- Modules of the Scrum Project
- Domain of the Scrum Project
- Scrum Project Statuses
- Application Examples
- Appendix
- Change History
-
FAQs
- Work Items
- Member Management
-
Troubleshooting
- Why Is the Message "You have been invited to run projects with another account. Accept invitation" Displayed When Inviting Other Users to Join My Project in CodeArts Req?
- Why Am I Prompted that the Service Is Disabled When Creating a Project with "DevOps Full-Process"?
- Why Is a Message Indicating the Field Name Already Exists Displayed When Setting a Work Item Field in a Scrum Project?
- Videos
- General Reference
Copied.
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 their total size cannot exceed 500 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
- 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.
NOTE:
After a bug is created, the people selected for Owner, Raised By, and Copy To will receive email and system 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.
Operation |
Description |
---|---|
Modify bug title |
Click |
Modify bug field |
Click the target field value in the row of a bug to modify the value. |
Duplicate bug |
Click |
Copy bug link |
Click |
Migrate bug |
Click
|
Collaborate on bug |
Click |
Delete bug |
Choose ![]()
|
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot