Code Review with Codebeamer
Summary
With Codebeamer it is possible to:
• Assign any code changes to issues (bugs, tasks) as described here: Tracing Source Code Changes to Requirements, Task and Bugs
• You can already apply custom Workflows: Version Control Workflows.
• Also you can manage workflows and code-changes using Pull Requests: Integration Manager Workflows & Pull Requests with Git and Mercurial.
Code reviews are an efficient way to improve communication among developers, reviewers, and other team members. It aids in providing feedback to the original authors of a code modification, detecting bugs and other code issues early, and therefore considerably improving code quality.
Code Review for Pull Requests
When developers or a team completes a task, they submit a Pull Request to the master repository, signalling that the code is ready for integration. When the Pull Request is fired, the integrators and other team members have the ability to examine and review the new code modifications.
The code review is a straightforward activity, similar to adding a remark to an issue. The reviewer examines the Pull Requests and discovers the cumulative diff of the modifications. As the reviewer reviews the code, they can click on any code-line in the diffs and begin making comments there.
After the review comment is ready and saved the review is ready, and other collaborators will see it too. This shot shows how multiple comments from different authors look like:
The code-review comments are just like any regular comments, in fact these will become also comments on the Pull Request itself. This also means that all interested parties will be notified when a code-review comment is submitted.
So one can also view and even edit these comments on the Comments tab:
