About Review Hub
The Review Hub is a useful feature that allows you to review and approve Codebeamer work items. It ensures that these items meet the standards of quality, completeness, and feasibility. The tool comes equipped with several functionalities that make it a robust and comprehensive tool for managing and approving work items throughout the software development lifecycle.
The Review Hub can streamline review processes, foster collaboration among stakeholders, and maintain transparent documentation. By empowering teams to deliver high-quality, user-centric products, it can help organizations achieve their goals efficiently.
A review in Codebeamer is a collection of items in a Tracker, Release, or Report. These items have a specific version depending on the time the review was created. The review items can be a collection of different work items or a single item.
Generally, a review process in Codebeamer involves the following steps:
• Preparation and Creation: Before starting the review process, ensure that the set of items such as tasks, requirements, or change requests have the relevant details. When these items are ready for review, you can start the review creation process.
• Adding Contributors: During the review creation and editing process, you can add contributors to the review. Contributors play a crucial role in deciding the status of each review item. They can approve, reject, or request further work on an item.
• Updates and Notifications: If an item is modified during the review process, the selected contributors receive notifications about the change. As a reviewer, you can decide whether the review needs to be restarted or if it can continue with the modified item. You can also restart the entire review, complete the review, or review only the items that have been modified since the review started. For more information, see
Reviewing Items
• Completion: Once all contributors have updated the status of review items, the review can be accepted or rejected based on the status. You can then complete the review process. For more information, see
About Item Status Thresholds
Contributors in a Review
Contributors are the key drivers of the review process. They are responsible for reviewing, approving, and rejecting the work items.
You can select and add users, groups, or project roles as contributors to a review while creating or editing reviews. You can also select all the project roles from projects involved in the review as review participants. When you add a role or group to the review, all the members of that role or group can review the items, moderate the review, or carry out both reviewing and moderating actions. However, each user can see only the review items to which they have read or view access.
There are two types of contributors for each review:
• Moderators: Have permission to review items and edit the review. They are responsible for reviewing, approving, and rejecting the work items. In addition, they can restart and close a review.
• Reviewers: Have permission to review items but have no permission to update the review. They can approve or reject the review items and add review comments.
Viewers
Viewers are also participants in the review process. They can only view the review, but cannot review the items. For a viewer, a review opens in the read-only mode. Some common roles such as: Project Admin, Product Owner, Scrum Master, Developer, QA, Test Lead, Test Engineer, Hardware Engineer, Hardware Leader, Product Approver, Software Engineer, Software Leader are preselected as viewers by default. A system administrator can change the name of the preselected roles in the Application Configuration, or can disable it.