Creating a Code Review

Typically, you will want to create a Code Review after you have created a Story/Task in Rhythm and you have associated that Story/Task with a specific file or change set during your SCM commit. How to associate your commit with the Story depends on your SCM tool. To associate a Story/Task with files during a commit, depending on your SCM tool, see StarTeam or Git. If you already performed a commit and didn't associate it with a Story during the commit, see Add Existing Commit to a Code Review.

Important: Each Story/Task can contain only one Code Review.

To create a Code Review:

  1. For a Story/Task in Rhythm that does not have change sets associated, click GUID-E5A11DAB-2D51-4C04-AAC0-B849DE1767C3-low.png Action > Create Review. In Scum, this menu is available on the Story or Task row in the Grid. For Kanban, this menu is available in the Story card. The following resulting card is for a Kanban Story:

    GUID-DBDE0F9D-C101-4B35-88B1-6D1EC61CF187-low.png

  2. For a Story that already has a change set associated, click the Change Set icon GUID-7C5D8A99-6430-4833-8FE6-56B9FDCC82F6-low.png for the Story. The following example is from the Sprint List view.

    GUID-520C000B-F2B2-44D5-8B97-BDEB20FE743C-low.png

  3. After you click the icon or agree to create a Code review, the Code Review window opens:

    GUID-6D893BBA-D8DD-4752-828E-80F1EE250078-low.png

    If you have already associated a commit with the Story, the files in the commit will appear in the View by list.

  4. Use the Code Review Editor to complete the Code Review process.
Tip: When you create a Code Review, it will appear in the Relationships tab of the Story Editor.

GUID-F8AE033C-BEF4-41B0-BF26-9BA3842B7C0C-low.png