When creating a Requirement, there is a No Review Required checkbox. If this option is selected, the Requirement is created directly in Active status.

In most cases, however, Requirements still need to go through review.

• Even if a Product is fully managed by one person, early ideas can still be saved as drafts and reviewed later.
• During development and testing, teams may identify Requirements that need optimization. New Requirements submitted in this process should be reviewed.
• Technical support teams may collect new Requirements from users or customers during communication, and those Requirements also need review.
• Any changes to the title, description, acceptance criteria, or attachments of a Requirement should go through the change process. After a change is made, the Requirement status becomes Changed and the Requirement must be reviewed again.

To learn how product managers review Requirements in Sanplex, you can watch the video below:

（视频介绍）

This section explains the workflow and methods used for Requirement reviews.

I. Configure review rules, workflows, and outcomes

Review rules, workflows, and outcomes for Requirements can be viewed and configured under Admin > Feature Settings > Product > Business Requirements / User Requirements / Development Requirements.

图1

Click Review Rules to configure review rules and Super Reviewers. Super Reviewers are not restricted by any review rule and have veto power. Multiple Super Reviewers can be selected.

图2

Review outcomes can be customized. However, because these values are used in system calculations, you can modify existing outcomes but cannot add new custom outcomes.

图3

The review workflow can be enabled or disabled. It is enabled by default. When the workflow is enabled, you can specify users, roles, and departments that do not need to go through the review workflow.

图4

The review workflow can also be disabled. When it is disabled, you can still define users, roles, and departments for mandatory review. Requirements submitted by those users must still go through review.

图5

II. Requirement reviewers

When creating or editing a Product, you can define default reviewers for that Product. When Requirements under that Product are created, edited, or changed and require review, those Product reviewers are used as the default reviewers.

You can assign either a single reviewer or multiple reviewers.

图6

If reviewers have been configured for the Product, only those reviewers can be selected when creating, editing, or changing a Requirement. If no Product reviewers are configured, any user with access to the Product can be selected as a reviewer.

图7

III. Super Reviewers for Requirements

Under Admin > Feature Settings > Product > Business Requirements / User Requirements / Development Requirements > Review Rules, you can configure Super Reviewers. Super Reviewers are not restricted by any review rule and have veto power. Like regular reviewers, multiple Super Reviewers can be configured.

图8

Even if a Requirement has already been reviewed by multiple reviewers and review comments have been generated, a Super Reviewer is still not restricted by the previous review rules. The Super Reviewer’s result becomes the final result for the current review round.

The Requirement history also records the time, comments, and result of the Super Reviewer’s review.

For example, if earlier reviewers rejected a Requirement, but a Super Reviewer later reviews it and approves it, the final review result for that round becomes Approved.

图9

IV. Multi-reviewer Requirement reviews

When a Requirement is created or changed, multiple reviewers can be selected. The rule used to determine the final result in a multi-reviewer scenario is configured in the background. Whether the Requirement passes review is calculated based on both the configured review rule and the actual review results submitted by reviewers.

1. Configure review rules

Review rules can be selected under Admin > Feature Settings > Product > Business Requirements / User Requirements / Development Requirements > Review Rules.

Two rules are supported:

• The Requirement is approved only if all reviewers approve.
• The Requirement is approved if more than half of the reviewers approve.

图10

2. Multi-reviewer review when creating a Requirement

When creating a single Requirement, you can select multiple reviewers:

图11

When creating Requirements in batch, you can also select multiple reviewers:

图12

• After writing the Requirement, if you click Save as Draft, the Requirement status becomes Draft. If you click Save, the Requirement status becomes Under Review.
• After all reviewers complete their reviews, the system calculates the result based on the configured review rule and then determines whether the Requirement status needs to change.
• The system first checks whether the Requirement passes review according to the configured all approved or more than half approved rule. If it passes, the Requirement status changes to Active.
• If the Requirement does not pass review, the result is determined by vote distribution. If Reject receives the most votes, the Requirement is rejected and its status changes to Closed. If Needs Clarification receives the most votes, the Requirement returns to Draft so it can be revised and submitted again for review.

图13

3. Multi-reviewer review when changing a Requirement

When changing a Requirement, you can also select multiple reviewers.

图14

A changed Requirement can be saved temporarily, and its status becomes In Change.

After it is submitted for review, the Requirement status becomes Under Review.

Once all reviewers complete their reviews, the system calculates the result based on the configured rule and then determines whether the Requirement status needs to change:

• The system first checks whether the Requirement passes review according to the configured all approved or more than half approved rule. If it passes, the Requirement status changes to Active.
• If the Requirement does not pass review, the result is determined by vote distribution. If Revert Change receives the most votes, the change is rejected, the Requirement content is rolled back to the previous version, and the Requirement status changes back to Active. If Needs Clarification receives the most votes, the Requirement returns to In Change so it can be revised and resubmitted for review.

图15

V. Withdraw a Requirement review

After a review has been initiated, if you find that the Requirement title, description, acceptance criteria, or attachments still need to be modified, you can withdraw the review. This helps avoid multiple unnecessary review rounds.

To use Withdraw Review, you must first grant the corresponding permission under Admin > User Management > Permissions > Permission Groups.

图16

In Product > Requirement List, a Requirement that has entered the review process will display a Withdraw button in the action column.

图17

After you click Withdraw Review, the Review button changes to Submit for Review, and the Withdraw Review button becomes disabled. You must make changes again and resubmit the Requirement for review before it can re-enter the review workflow.

图18

The Requirement history records the withdrawal action and the subsequent resubmission for review, making the process easier to trace and review later.

图19