CodeArts Req
CodeArts Req
- 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
- Getting Started
-
User Guide
- CodeArts Req Usage Process
- Purchasing and Authorizing CodeArts Req
- Accessing the CodeArts Req Homepage
- Creating a CodeArts Project
- Managing Scrum Project Requirements
-
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 Roll-up Rules
- Configuring Notification Rules
- 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 Roll-up Rules
- Configuring Notifications
- 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
-
APIs
-
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
- User Information
- Project members
- Project Information
- Project Indicators
- Project Statistics
- Modules of the Scrum Project
- Domain of the Scrum Project
- Scrum Project Statuses
-
Work Items of the Scrum Project
- Application Examples
- Appendixes
- Change History
-
FAQs
-
Work Items
- How Can I Assign One Scrum Project Work Item to Multiple Members?
- Why Is a Message Reporting Duplicate File Name Displayed During File Association in a Scrum Project?
- How Do I Handle the Verification Exceptions in the Number of Work Items Imported to an IPD Project?
- How Do I Modify the Recipient After an IPD Project Requirement Is Assigned?
- 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 Can't I Create a Project Using "DevOps Full-Process"?
- Why Is a Message Indicating the Field Name Already Exists Displayed When Setting a Work Item Field in a Scrum Project?
-
Work Items
- Videos
- General Reference
On this page
Show all
Help Center/
CodeArts Req/
User Guide/
Managing IPD-System Device Project Requirements/
Tracking the Project Progress/
Using Bug Measurement
Copied.
Using Bug Measurement
You can use bug measurement to track the defect progress.
Viewing the Bug Measurement
By default, the bug measurement view displays the following statistical charts: bug overview, legacy DI trend, accumulated bugs, bug daily throughput, bug distribution by severity, bug distribution by status, and top 8 owners with legacy bugs.
- Numerical statistical charts: The indicator value represents data for all work items in real time. For example, the total number of bugs in Bug Overview is equal to the total number of bugs during statistics collection.
- Trend charts: The indicator value represents the daily data. For example, the total number of legacy bugs on June 7 in legacy DI Trend is equal to the total number of legacy bugs on June 7.
The following table lists the statistical charts in bug measurement.
|
Statistical Chart |
Data Description |
|---|---|
|
Bug overview statistics |
Collects statistics on the number of bugs whose states are processing, completed, and overdue and whose severities are severe at the current time. Click a number to view the corresponding list. |
|
Legacy DI trend |
Collects statistics on the DI trend of legacy bugs in the selected time range.
|
|
Accumulated bugs |
Shows the trends of accumulated bugs found, resolved bugs, and legacy bugs. Cumulative number of legacy bugs = Cumulative number of found bugs – Cumulative number of resolved bugs. |
|
Bug daily throughput |
Collects the number of bugs found and fixed in the selected time period. |
|
Bug distribution by severity |
Collects statistics on the number of bugs by severity at the current time. |
|
Bug distribution by status |
Collects statistics on the number of bugs by status at the current time. |
|
Top 8 owners with legacy bugs |
Collects top 8 owners of legacy bugs at the current time and displays the bug number. |
Parent topic: Tracking the Project Progress
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot
