Contributions
Allow 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.3.2KViews1like0CommentsAllow 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 > allowthe participant to sort the existing 'Status' and 'Changed lines' columns in descending order to focus on key changes.3.5KViews2likes0CommentsAllow reviewers to quickly filter the file list by file type
Hello, Our Dev team can create some reviews containing a lot ofvarious files (eg. *.cs, *.xml, *.csproj, *.config...). When reviewing the files under the 'Review Materials' section, we would like to filterthe 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 changesin our .csproj files. In such cases, we would like to see at one glance the modified .cs files. Thanks Thomas13KViews6likes3CommentsRe: 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 revieweverything 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' sectionwhere 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.13KViews0likes0CommentsAllow 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 inconvenientwhen the number of branches increases.Thereare also some really irritating cases : When you add Git Diffs to existing reviews and have toselect 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 Thomas7KViews5likes1Comment