Updated on 2025-07-22 GMT+08:00

Creating a CR for RRs/Bugs

Finally, this section describes how to create a CR for controlled fields of raw requirements and bugs. The CR processes for bugs and raw requirements are the same. This section covers only the bug CR.

Creating a CR for Bugs

Bugs are classified into two categories: those that do not require cross-project collaboration and those that do. Each category has its own change process. For details, see Creating a CR for Bugs Without Cross-Project Collaboration and Creating a CR for Bugs with Cross-Project Collaboration.

The bug CR process is as follows.

Figure 1 Bug CR process

Creating a CR for Bugs Without Cross-Project Collaboration

Table 1 Process of creating a CR for bugs without cross-project collaboration

Process

Description

Step 1: Triggering a Change Review for Bugs Without Cross-project Collaboration

On the bug details page, edit fields with and click OK in the displayed dialog box.

Step 2: (Experts) Reviewing the CR for Bugs Without Cross-Project Collaboration

Review experts complete the CR.

Step 3: (Approver) Making Decisions on the CR for Bugs Without Cross-Project Collaboration

The approver makes decisions on the CR.

Step 4: Bug Field Values Changed Automatically upon Approval

The corresponding fields are changed automatically based on the CR conclusion.

Table 2 lists the roles required for bug change review without cross-project collaboration.

Table 2 Project roles

Member

Role

Responsibility

Sarah

Project creator (product owner)

Creates a project and sets up a team.

Caleb

Test manager

Approves the CR.

Gabby

Developer

Initiates the CR.

Sam

Tester

Serves as a review expert of the CR.

Betty

Tester

Serves as a review expert of the CR.

Tom

Tester

Serves as a review expert of the CR.

Creating a CR for Bugs with Cross-Project Collaboration

For cross-project bugs, the change review process is different.

Table 6 Process of creating a CR for bugs with cross-project collaboration

Process

Description

Step 1: Triggering a Change Review for Bugs with Cross-project Collaboration

On the bug details page, edit fields with and click OK in the displayed dialog box.

Step 2: (Experts) Reviewing the CR for Bugs with Cross-Project Collaboration

Review experts complete the CR.

Step 3: (Approver) Making Decisions on the CR for Bugs with Cross-Project Collaboration

The approver makes decisions on the CR.

Step 4: Bug Field Values Changed Automatically upon Approval

The corresponding fields are changed automatically based on the CR conclusion.

Table 7 lists the roles required for bug change review with cross-project collaboration.

Table 7 Roles in bug change review with cross-project collaboration

Member

Role

Responsibility

Sarah

Current project creator (product owner)

Creates a project and sets up a team.

Bob

Test manager of the project where the bug is proposed

Approves the CR.

Bree

Current project developer

Initiates the CR.

Eddie

Bug proposer

Serves as a review expert of the CR.

Paul

Project tester who finds the bug

Serves as a review expert of the CR.

Zach

Project developer who finds the bug

Serves as a review expert of the CR.