Collaborator Feature Requests

Hello,   Would it be possible to find an easy way to let to Reviewer know which files have been updated in a review? Right now the Reviewer must click on the files to see what has changed. Could the "added/changed/deleted" numbers be a difference from the last reviewed/accepted revision as opposed to a running count of all modifications to the file? Even a visual indicator like (*) next to updated files with changes from the previous reviewed/accepted would be sufficient. As things are now, it's a really chore to review code using Code Collaborator.   Thanks. ... View more

The main portal filter for reviews is pretty basic, we’d like to see increased functionality in this while searching or filtering reviews for each user. a. Time based filters (last updated, created etc.) b. Ability to tag & group set of code reviews (helps when there are multiple code reviews for some big feature) c. Filter based on above mentioned tags ... View more

Usually we have a list of SVN revision numbers affected by an issue or change request.   To start a review I'd like to copy this list into the Collaborator Client GUI and just go on with the review.   But the tool stops creating the review when there is one SVN revision number in the list where only SVN properties where changed.   Perfect would be to just continue importing when one SVN revision does not contain any files. (maybe just report the SVN revision numbers without file changes afterwards as a list)     I already contacted support and it seems that this is a "feature" so I wrote this new "idea" 🙂   ... View more

It would be nice to run the installer with triggers that could preset the server, username, tray icon, proxy settings and such in a way that would be quick to implement.   collabinstaller.exe -url -collab.domain.com:8443 -tray yes -proxy 127.0.0.1   etc... ... View more

It would be helpful if there was a third state to indicate that a defect has been resolved, but still needs to be "approved" (marked Fixed) by the author of the defect. Currently a defect only appears as "Open" or "Fixed" in the Defect Log. It is difficult to tell which defects have been resolved without looking through the comments, or having someone tell you to look at a specific defect. When there are a lot of defects in the Defect Log, a third state to filter on would make it easy to identify those defects that need to be marked Fixed. Maybe this could also be shown with a different color bug, instead of red or green.      ... View more

I am requesting an enhancement to the filters. I would like to see the creator filter become a multi select filter instead of a single select filter. ... View more

Currently a pull request from Bitbucket can only be added to the Remote System Links section automatically when the pull request is created, and there isn't a way to add a link to a pull request manually. Is it possible to make an update that allows linking of more than one pull request in a single review? In the case of making small related changes across multiple repositories, it would be very beneficial to be able to include more than one pull request in a single review, to allow those changes to be reviewed as a set. ... View more

We would like only specific non-admin users to be able to reopen reviews. This could be a user-specific permission or allow all group admins to reopen. The current template level open either allows all participants or system admins to reopen. We cannot allow all participants to reopen but it is a burden on admins to perform these. ... View more

We would like a dedicated search option (not the built-in browser search). This would enable searching in different tabs in excel and searching though all documents.  ... View more

We utilize the assignee field on defects to drive action items.  However, we have not been able to find a way that this is communicated in any method outside of the actual review.  Having this on the home page and/or notification activity (tray, in app, email) would help to expedite action. ... View more

When I am writing out a comment on a review in response to another comment, my comment is deleted if another user updates that thread.  This is incredibly annoying if I'm writing out a detailed response as there's no way to recover what I'd typed up to that point. The draft comment should be retained in some form when the thread is updated. ... View more

From the content review page (while reviewing a specific document), I would like the ability to go to a specific defect number using ctrl+g or via the search bar. This will allow me to quickly navigate defects in the document. ... View more

I would like a feature to be implemented so every person from a group can be added to a review without the user having to individually type in each name. I am aware of review pools, but we're not wanting to wait for reviewers to "take" a review seat, we just want to be able to invite a large group of people to a review and give them the option of reviewing the document. For example, we currently have a list of individuals that are invited to every peer review regardless of content. Currently to invite all of them it requires the Author to input over 40 names by hand. It would be much easier if the Author could just type in a single name (like a group name) and have all 40 reviewers be automatically added.   ... View more

Could the property be allowed to add defect to the role template? There may be cases where the person assigned as Author should not open the defect. As an example, the Author can only fix the defect or reject defect. ... View more

We have recently upgraded our Collaborator server to 9.4.9400 with the update site 8.4.8406.001. Below are the observations: 1. We have archived review items older than 3months old and as a reviewer we have old review items with different status that are not required on the web display dashboard. Is there any mechanism to eliminate this issue as this is causing a confusion for the reviewers when they are having more than 100 review items on their home page/dashboard? 2. As part of RTC/QNX integration, developers change code in the RTC/QNX system -> attached an existing work item to the change - > then submit for a review. During this, in the backend collaborator is loading all the existing review items and also the archived items which is taking more than 15min in creating a review. This is causing a performance issue on RTC/QNX side. ... View more

Edit Defect / Comment box falls off the bottom of the screen when the item you are entering is near the bottom of the page.  This could be easily missed and if not missed requires user to scroll down the page in order to take required action. Change the window scroll point to ensure the comment/drop downs are specified when creating the defect (not the best screenshot below but close enough).   ... View more

The comments are not easily distinguished from each other.  Create a space or highlight more clearly the comment/action that is currently active. Can we add some sort of delimiter/space to separate bug comments? ... View more

I frequently keep one browser (on Windows) open to a review I am creating using the Linux GUI client to upload files to the review.  Uploading from subversion workspace might take a number of uploads from various project root directories.  I am always dismissing the browser after the launch of each one.  It would be nice to have a persistent preferences setting to speficy whether or not to launch a browser after uploading. ... View more