ContributionsMost RecentMost LikesSolutionsAllow participants to filter files having comments or defects Once a review has been created and participants provided comments, it will be nice for them to only show and focus on the files that have comments or defects. This can help them to spot the on-going discussions without scrolling up and down thru a huge list of files. This could be implemented like the existing 'Overlay' toggle button that is located in the 'Review Materials' section. Allow participants to sort the 'Review Materials' grid by the 'status' and 'changed lines' columns The existing grid under the 'Review Materials' section is rigid. It does not allow the participants to quickly identify key changes. For instance, a participant might have to scroll thru the a huge changelist to identify files having reworked changes or many affected lines. Solution > allow the participant to sort the existing 'Status' and 'Changed lines' columns in descending order to focus on key changes. Allow reviewers to quickly filter the file list by file type Hello, Our Dev team can create some reviews containing a lot of various files (eg. *.cs, *.xml, *.csproj, *.config...). When reviewing the files under the 'Review Materials' section, we would like to filter the files by their extension types so that we can focus on the most important changes. For instance, we can have just a few critical changes located under some .cs files and many unimportant changes in our .csproj files. In such cases, we would like to see at one glance the modified .cs files. Thanks Thomas Re: Filter review materials by file extension type The intent for this feature is not to hide unimportant files from a review. We still want to review everything that affects a compilation. As you suggested, we only want reviewers to be able to focus on specific files more quickly. For example, this can be achieved with a 'Filter' combo box in the 'Review Materials' section where the user specify the available extension types (.cs, .xml...) he wants to see. The ultimate goal is to have a user-friendly 'Review Materials' section that helps users to find and review specific files without scrolling up and down thru a huge list of files. Allow to pre-fill the 'Before' and 'After' branches in Code Collaborator Client Hello, The Collaborator Enterprise Client's "Add Git Diffs to Review" modal window allows to specify Diffs to review by selecting the Before branch and After branch. We can browse thru existing branches thanks to the drop-down lists (see attached snapshot), but this can quickly become inconvenient when the number of branches increases. There are also some really irritating cases : When you add Git Diffs to existing reviews and have to select the same branches over and over again. Solution > Persist the latest selected branches for a given existing review and user and allow to have the branches pre-filled When your DevOps guidelines require you to create reviews against a 'Develop' branch systematically. Therefore, you always have to set the 'Before' branch on this 'Develop' branch. Solution > Configure a default 'Before' branch so that it can automatically be picked up for new reviews. Thanks Thomas