1 Download and Upgrade to 15.0+ Series
2 New Features of ZenTao 15 Series
3 Interface Changes of 15 Series
4 Update to the Latest Version
5 Quick Start of 15 Series
6. Basic Application of Version 15
6.1 Beginner
6.2 Add Integrally
6.3 API Library
7. Base On The Roles
7.1. Admin
7.1.1 Edit Departments and Team Members
7.1.2 Edit Users
7.1.3 Edit Privilege
7.2. Program Leader
7.2.1 Create a Program
7.2.2 Link to Products
7.2.3 Create a Project
7.2.4 Manage Staffs
7.2.5 Add a Program Stakeholder
7.3. Product Owner
7.3.1 Create a Product
7.3.2 Edit Modules
7.3.3 Product Multi-branch/Platform Management
7.3.4 Edit Plans
7.3.5 Edit Stories
7.3.6 Review a Story
7.3.7 Create a Release
7.3.8 Tracking Progress
7.4. Project Manager
7.4.1 Edit Projects and Execution
7.4.2 Edit Teams
7.4.3 Link to Stories
7.4.4 Split Tasks
7.4.5 Tracking Progress
7.4.6 Waterfall Project
7.4.7 Kanban Project
7.5. Development Team
7.5.1 Apply for Tasks and Bugs
7.5.2 Update Status
7.5.3 Complete Tasks and Bugs
7.5.4 Submit Codes
7.5.5 The General Kanban, Story Kanban, Bug Kanban, and Task Kanban
7.6. Test Team
7.6.1 Edit Users' Case
7.6.2 Execute Users' Case
7.6.3 Submit a Bug
7.6.4 Test and Close a Bug
8. DevOps Features
8.1 Git/SVN Repository Management and Viewing Code
8.2. Integrate GitLab
8.2.1 Integrate GitLab, Bind Users, Link to Issues and Create a Build
8.2.2 Integrate GitLab and Submit the Merge Requests
8.2.3 GitLab Privilege in ZenTao
8.3 Integrate Jenkins and Create a Build
8.4 Integrate SonarQube
9 General Kanban
10. Backstage Settings of Version 15
10.1 Desktop
10.2 Model
10.3 Custom
10.4. Message
10.4.1 Mail
10.4.2 Webhook
10.4.3 Browser
10.4.4 Settings
10.5 Extension
10.6 Secondary Development
10.7 System
10.8 Import Jira Data
10.9 Registration Menu and Privilege
11. Privileges Management and Access Control of Version 15
11.1 Privileges Management and Access Control for Programs
11.2 Privileges Management and Access Control for Products
11.3 Privileges Management and Access Control for Projects
11.4 Privileges Management and Access Control for Executions
11.5 Access Control and Data Relationships for Projects and Executions

Review a Story

2022-01-10 18:37:56
Hongyan
851
Last edited by philip on 2022-06-23 17:43:46
Share links
Summary : How to review a story as one product owner
There is a "no review required" check box when creating a requirement. The status will be activated after the requirement is successfully created if this check box is checked.

But in most cases, the requirements still need to be reviewed.

Even if one person owns the product, it's okay to save some half-baked ideas as drafts and work on them later.
Development and testing In the actual development and testing work, some requirements that need to be optimized will be found according to the specific work, and the new requirements submitted must be reviewed.
When technical support connects users and customers, they will obtain new requirements from users and customers, and the unique requirements submitted by them also need to be reviewed.

Any modification to the requirement title, description, verification criteria and attachments should go through the change process. After the change, the status of the requirement is changed and needs to be reviewed.

This document will introduce the review process and method of requirements.

1. Rules, process and results of requirements review

The review rules, processes, and results of requirements can be viewed and set in the background-customization-requirements.

Review Rules:

Result of review:

Review process:
The review process is enabled by default. Whether you open or close the review process, you can set a mandatory review.
The members in the mandatory review and the submitted requirements must go through the review process.

2.The reviewers

When creating and editing products, we have added a new field for product reviewers.
If a product reviewer is set, when a requirement is created or changed under the product, and a review is required, the default reviewer is the appointed product reviewer.

The reviewer can set up one person or multiple people.

After the reviewers are set, when creating requirements and creating requirements in batches, only the set reviewers are displayed in the Who Reviewed drop-down list.

When changing requirements, who will review the settings also lists the reviewers by default.

3. Super requirements reviewers 

ZenTao version 16.0 has added the super reviewer function.
Super reviewers are not subject to any review rules, and super reviewers have veto power.
Super reviewers can set up as many people as reviewers.

In the admin--custom--review rules--super reviewer, you can set our super reviewer.
Even if the requirement has been reviewed by multiple people before, and one of the reviewers has reviewed and rejected it, when the super reviewer reviews the requirement, Not limited by the previous review rules, the final result of the super reviewer's review is the final result of this round of requirements review.
The requirement history also records the time, review comments, and results of the Super Reviewer review.

4. the requirement for multi-person review

When requirements are created and changed, who will review them can choose multiple people. Previously, only one person could review, but now multiple people can review a requirement.
When multiple people review requirements, review rules are set. Whether the requirement is reviewed or not is calculated according to the review rules and the review results of the actual reviewers. Finally, the review results of the requirements are obtained.

4.1 Setting Review Rules

Review rules can be selected in the admin--custom--requirements--review rules.
We provide two kinds of rules: when all the review results are passed, the requirement is passed by the review (all passed); when more than half of the review results are passed, the requirement is passed by the review (more than half passed).

4.2 Multi-person review when creating requirements

When creating requirements individually and in batches, who should review them can choose multiple reviewers.
When creating a requirement individually:

When creating requirements in batches:

After successfully creating a requirement for multi-person review, the status of the requirement is draft.
When all reviewers have completed the review, after calculating the result according to the review rules, it is judged whether the status of the requirement needs to be changed according to the result.

4.3 Multi-person review when changing requirements

When changing requirements, multiple people can also be selected for review.


The changed requirement status becomes changed,
When all reviewers have completed the review, after calculating the result according to the review rules, it is judged whether the status of the requirement needs to be changed according to the result.

4.4 Reviewers review requirements and calculate review results according to review rules

The requirements for multi-person review, who reviewed the requirements can be viewed in the life of the requirements on the requirements details page.
Those who have been reviewed are grayed out, and when the mouse is hovered, they are prompted to be reviewed, and those who have not been reviewed are prompted to be reviewed when hovering the mouse.
Next, let's take 3 people reviewing a requirement as an example, and look at the multi-person review of the requirement according to different review rules.

4.4.1 When the review rule is: "All passed" passed
When the review results of the three people are all confirmed and passed, according to the calculation of the review rules, the review result of the requirement is confirmed to pass, and the status is changed to active.

When the review result of 2 people is confirmed to pass, and the review result of 1 person is to be clarified, the calculation result of the requirement review according to the review rules is that the review is not passed, and it remains as a draft.

4.4.2 When the review rule is: more than half pass

The following requirements are reviewed by 3 people, the result of the review by 2 people is confirmed, and the result of review by 1 person is rejected.
According to the rule calculation, the system determines that the review result of this requirement is confirmed, and the requirement status changes from draft to active.

When the review result of 2 people is not passed, and the review result of 1 person is passed, the system determines that the review result is not passed, and the status of the requirement remains as draft.

4.4.3 Other situations
If 1 reviewer has been reviewed by 3 reviewers, then edit the requirements and delete the remaining 2 reviewers.
Then the requirement will be the result of the final review of the requirement according to the review result of one person who has been reviewed.

5. Revocation Review of Requirements
After the requirement is reviewed, if it is found that the title, description, acceptance criteria and attachments of the requirement still need to be revised.
To avoid multiple rounds of review.
We provide the revocation review function. First, you need to go to the admin--member--privilege privilege group to assign the permission to revoke the review.


Display the Cancel button in the action bar of the requirement that initiated the review in the Product--Requirement list.

After clicking the Cancel Review button, the Review and Cancel Review buttons are grayed out.
It needs to be changed again, and the review process can be continued only after the review is initiated.

The historical information of revoked reviews and re-initiated reviews will be recorded in the requirement history.
Easy to trace and view operations.

Write a Comment
Comment will be posted after it is reviewed.