- 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
Copied.
Configuring Work Item Status Flows
Prerequisites
An IPD-standalone software project is available, and you have permission to configure status flows for the project.
Configuring Work Item Status Flows
- This function is currently available for R&D requirements, system features, tasks, and bugs. The following describes how to customize a bug status flow.
- System status flows can only be viewed. You can copy them to customize a new one. Custom status flows can be edited and executed to meet your service requirements.
- If an R&D requirement is switched to a custom status flow, the rollup rule will automatically become invalid. Only when all types of work items of the R&D requirement are executed in the system status flow, the rollup rule will apply.
- Access the CodeArts Req homepage.
- Go to a project and choose Settings > Work.
- In the navigation pane, choose Work Items > Bug > Status Flows.
- Click Edit. The Bug Status Flow Configuration canvas page is displayed with the default system status flow.
Figure 1 Bug status flow
- Copy a system status flow to customize a new one.
Figure 2 Copying to create a status flowFigure 3 Customizing a status flow
- Click Edit, then double-click any status or transition line to display their rules.
Figure 4 Configuring status nodesFigure 5 Configuring transition lines
- Click Edit, and add a status.
- Expand the status drawer. Drag any available status to the canvas or click
to add one.
Figure 6 Expanding the status drawerFigure 7 Expanded status drawerFigure 8 Adding a status - Click the Name drop-down list, and then click Create Status.
You can also select an existing tenant-level custom status.
Figure 9 Creating a status - Set Name and Category.
The options include To Do, Doing, and Done.
- Click OK.
The new status is displayed on the bug status flow canvas.
Figure 10 Adding a status to a bug status flow
- Expand the status drawer. Drag any available status to the canvas or click
- Drag the new status to a proper position, draw a transition line with your mouse, and enter a name.
Figure 11 Adding a transition line for a new status
- Double-click the new transition line.
Figure 12 Transition line configuration panel
- Set Transition Line Name and other information.
- After the configuration is complete, click
to collapse the panel.
Figure 13 Collapsing the transition line configuration panelThe new status must have at least one incoming and one outgoing transition lines. To add a transition line, repeat steps 5 to 8.
Figure 14 Adding incoming and outgoing transition lines - Click Execute in the upper right corner, and customize the main navigation bar.
Figure 15 Setting the main navigation bar
- Click OK.
The new bug status flow is displayed on the Status Flows tab page.
Figure 16 Bug status flowsThis status flow will be applied to the bug management process.
Figure 17 Status flow on the bug details page
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