Creating and Approving CRs

Constraints

• A maximum of 20 reviewers can be added.
• A maximum of 50 objects can be added to or associated with a single review ticket.

Tutorial Video

This video uses a baselined R&D requirement as an example to demonstrate how to create and approve a CR.

The UI may vary depending on the version. This tutorial is for reference only.

Creating a CR

1. Access the CodeArts Req homepage.
2. Create a CR in either of the following ways:
   • On the project homepage, go to the raw requirement, feature tree, R&D requirement, or bug list page, select a controlled raw requirement or bug, or a baselined system feature or R&D requirement, and modify a parameter marked with the icon. In the displayed dialog box, click OK.
   • On the project homepage, choose Review > Change Review. Then click CR.

3. On the CR page, set the required parameters.

   Table 1 Creating a CR

   Parameter	Description
   CR 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.
   Completion Time	The time when you want the review to complete.
   Copy To	Select the project members you want to inform about this review.
   Review Objects	Add the objects to be reviewed. RRs and bugs: You can only add RRs and bugs that are defined by the responsible project workflow and belong to the status node with editable controlled fields. Then, modify the controlled fields (marked with the icon) of the requirement change, and select the Decision-Maker and Reviewer. For work item types other than RRs and bugs: After adding the objects, modify the controlled fields (marked with the icon) of the requirement change, or move the work items into or out of a baselined release or sprint, and select the Decision-Maker and Reviewer. Change types include Move in/out of a baseline release or iteration, Modify, and Delete. Move in/out of a baseline release or iteration: The release or sprint becomes a baseline after the change, or the release or sprint is a baseline before the change. Modify: Modify the baseline lock field of a baseline work item. Delete: Delete a baseline work item. RRs and bugs: Only Move in/out of a baseline release or iteration and Modify are supported. Work item types other than RRs and bugs: All change types are supported, including Move in/out of a baseline release or iteration, Modify, and Delete. For work item types other than RRs and bugs: When Require Decision-Making is enabled, Decision-Maker is mandatory. If Review Expert is not set, the review phase will be skipped. You can configure Decision-Maker by referring to Configuring Reviews. By default, the options are Project Admin and Project Manager. You can select only one option. If Require Decision-Making is disabled, Review Expert is mandatory. If Decision-Maker is not set in the review ticket, the review process will skip the Pending Decision-Making phase. You can configure Review Expert by referring to Configuring Reviews. Multiple options can be selected. NOTE: You can configure Require Decision-Making by referring to Configuring Reviews. For RRs: If the proposing project initiates a change review, the options for Decision-Maker include the project administrator, project manager, and requirement owner of the responsible project. You can select only one option. If the responsible project initiates a change review, the options for Decision-Maker include the project administrator, project manager, and requirement submitter of the proposing project. You can select only one option. For bugs: If the proposing project initiates a change review, the options for Decision-Maker include the project administrator, project manager, test manager, and bug owner of the responsible project. You can select only one option. If the responsible project initiates a change review, the options of Decision-Maker include the project administrator, project manager, test manager, and bug creator of the proposing project. You can select only one option.
   Associated Files	Attachments, wikis, and documents related to the review. If the review objects include RRs and bugs, files can be associated only when the proposing and responsible projects are the same.
   Collaborative Parent Item Change	Existing change reviews you wish to collaboratively complete with the current review.

4. Click Submit.

   You can view the new CR in the change review list. For a new CR:

   • Click in the Operation column to copy the title, ID, current owner, status, and link information of the CR to the clipboard.
   • Click in the Operation column to copy the title link of the CR to the clipboard.

Related Operations

You can perform the following operations on a CR pending for submission.

Completing a CR

This operation is performed by the specified review experts and decision-maker of a CR.

1. Access the CodeArts Req homepage.
2. On the project homepage, choose Review > Change Review.
3. Click the title of a CR in the To Be Reviewed state. The CR details page is displayed on the right.
4. Click the icon in the row that contains the target review object, and set the required parameters.
   Figure 1 Review by review experts
   

   Table 3 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.

5. 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 CR is complete when one review expert approves or rejects it.
   • By all reviewers: A CR is complete when all review experts approve it or one review expert rejects it.
   • By pass rate: A CR 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 CR's result in the review phase is Rejected, the CR skips the decision-making phase and its final result is Rejected.

   After the review phase is complete for all review objects in the CR, the CR status changes to Decisioning.

6. Click the title of a CR in the To Be Approved state. The CR details page is displayed on the right.
7. Click the icon in the row that contains the target review object, and set the required parameters.
   Figure 2 Decision-making by decision-maker
   

   Table 4 Decision-making by decision-maker

   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 ticket to a new decision-maker.
   Comments	Your comments on the ticket. 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.
   Decision Maker	The new decision maker for this ticket. This parameter is displayed and required only when Transfer to others is selected.
   Expert Comments	Review result and reviewer comments for the decision-maker's reference.

8. Select Approve or Reject for Result, and click OK. The CR object's approval result is displayed after its decision-making process is complete.

   The CR status changes to End only after the decision-making process is complete for all review objects.

9. Perform the necessary operations on a Rejected review object in the completed CR.
   • On the CR details page, click Activate in the upper right corner. Then click OK in the displayed dialog box. All rejected objects in the CR have transitioned from the End state to the Resubmit state. The CR needs to be processed again.
   • In the second review process, you can check historical comments in the Resubmitting, Reviewing, Decisioning, and End phases.

     In the Review Objects area on the details page, click in the row where the target review object is located. In the displayed History Opinion dialog box, select a historical review comment from the Decision-Making Time drop-down list.

   • In the Review Objects area, click in the Operation column to remove objects that do not need to be re-submitted.

     When the last review object is removed, the re-review process is automatically canceled and rolled back from the Resubmit phase to the End phase of the previous round.

   • After modifying a review object, click Submit. In the Review Objects area on the details page, click in the row that contains the target review object to initiate re-review.
     1. In the re-review phase, you can click in the upper right corner and then choose to cancel the re-review. In the displayed dialog box, click OK. The review ticket is rolled back to the End phase of the previous round.
     2. In the decision-making phase, you can click in the upper right corner and then choose to cancel the re-review. Once a decision is made, the re-review cannot be canceled.

   • Perform 4 to 8 to complete the CR approval.