- 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
Show all
Copied.
Creating and Completing GRs
When your work items need to be reviewed, perform the following steps to initiate a general review.
Creating a GR
- Access the CodeArts Req homepage.
- On the project homepage, choose Review > General Review. Then click GR.
- On the GR page, set the required parameters.
Table 1 Creating a GR Parameter
Description
GR Title
Title of the review.
- Use letters, hyphens (-), underscores (_), commas (,), semicolons (;), colons (:), periods (.), slashes (/), parentheses, and spaces.
- Include 1 to 256 characters.
Description
Enter the background, value, and details of the review.
- Use text, images, or links.
- Include 1 to 50,000 characters.
Start time
The time when you want the review to start.
Completes
The time when you want the review to complete.
Require Decision-Making
This parameter is available only when Require Decision-Making is enabled on the Settings > Work > Review page.
If Require Decision-Making is set to No, no approver needs to be specified. The review will skip the decision-making phase.
Reviewer
The options of Reviewer can be configured on the Settings > Work > Review page. The default options are project administrator and project manager. You can select only one option.
Review Expert
If Review Expert is not set, the review phase will be skipped.
The options of Review Expert are project members. You can select multiple ones.
Copy To
Select the project members you want to inform about this review.
Associated Object
Add the objects to be reviewed, including raw requirements, system features, R&D requirements, and bugs.
Associated Files
Attachments, wikis, and documents related to the review.
- Click Submit.
You can view the new GR in the general review list.
Completing a GR
This operation is performed by the specified review experts and reviewer of a GR.
- Access the CodeArts Req homepage.
- On the project homepage, choose Review > Change Review.
- Click the title of a GR in the To Be Reviewed state. The GR details page is displayed on the right.
- On the details page, click Expert Review in the upper right corner. In the displayed dialog box, set the required parameters.
Figure 1 Review by review experts
Table 2 Review by review experts Parameter
Description
Result
Select your review result.
- Approve: You agree with the change.
- Reject: You do not agree with the change.
- Transfer to others: Transfer the review to another review expert.
Comment
Your comments on the change. This parameter is required when Result is Approve or Reject.
- Use letters, hyphens (-), underscores (_), commas (,), semicolons (;), colons (:), periods (.), slashes (/), parentheses, and spaces.
- Include 1 to 300 characters.
Expert Comments
Comments of other review experts.
- Select a review result (Approve or Reject) and click OK.
After the expert review is completed, the final review result can be determined using the selected method on the Settings > Work > Review page.
- By single reviewer: A GR is complete when one review expert approves or rejects it.
- By all reviewers: A GR is complete when all review experts approve it or one review expert rejects it.
- By pass rate: A GR is complete when "Number of review experts who approve the review/Total number of review experts × 100% ≥ Pass rate", or "Number of review experts who reject the review/Total number of review experts × 100% > 1 – Pass rate".
If a GR's result in the review phase is Rejected, the GR skips the decision-making phase and its final result is Rejected.
- Click the title of a GR in the To Be Approved state. The GR details page is displayed on the right.
- On the details page, click Decide by reviewer in the upper right corner. In the displayed dialog box, set the required parameters.
Figure 2 Decision-making by reviewer
Table 3 Decision-making by reviewer Parameter
Description
Result
Select your decision.
- Approve: You agree with the change.
- Reject: You do not agree with the change.
- Transfer to others: Transfer the review to another reviewer.
Comments
Your comments on the change. This parameter is required when Result is Approve or Reject.
- Use letters, hyphens (-), underscores (_), commas (,), semicolons (;), colons (:), periods (.), slashes (/), parentheses, and spaces.
- Include 1 to 300 characters.
Review Result
The result of the review phase for your reference.
Expert Comments
Results and comments of review experts in the review phase for your reference.
- Select Approve or Reject for Result, and click OK. The GR status changes to End.
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