Collaborator Feature Requests

Sometimes, you want a different person to look at something, or respond to a comment.  My team would like Collaborator to have a capability to tag another user.  For example, in Jira, you can use "@lastname,firstname" to tag another user.  We would like a similar capability in the comment boxes. ... View more

Very frequently comments are added in a review that need to be converted to defects.  The "ADD AS DEFECT" button is used but the defect text is blank.  In this use case, the comment is the defect.  This requires manual copy/paste, restating the comment, or adding a description of "see comment".   This product enhancement request is to pre-populate the defect text box when converting a comment to a defect.  This would steamline upgrading comments to defects. ... View more

User experience would be greatly improved if the reviewer could associate their comment or defect to a range of lines instead of just a single line.   Additionally, if that range could also be inclusive of characters within a single line that would also be appreciated.  When comments or defects are part of a large block of code being able to accurately call out an area of code instead of just a top line of code is helpful. ... View more

In the chat box of file foo.cc I would like to reference a specific line in file bar.cc. For example, I have bar.cc:line 12 written in my code collab chat box.    In this case, code-collab only recognizes and allows the jump to bar.cc, but not to the line. I would like a feature where a designer can write a reference to line 12 in bar.cc and Collaborator automatically auto-links the to the correct line.   ... View more

When you have a review with many files and many comments on each one, it would be nice to only see the files that you still have to review. On the "Review Materials" section, could we have a toggle button that would hide/display the files that the current user has accepted and that haven't changed since? In that same section, could we also have a way to hide all the lines that the current user already approved (and that didn't have any activity after the approval)? That way, for files with many comments, you would very easily find the ones you should review. This is slightly different from the current highlighting which is already quite good. ... View more

On large reviews, it can be hard for a reviewer to track which files they've completed reviewing, if there are defects or discussions still ongoing.  In that case, you don't want to mark the file as accepted, so it would be nice if there was a "Review completed for this version" button or flag. ... View more

This enhancement applies to Collaborator, version 9.4     In document reviews, the new pushpins are being rendered with opaque background.  The white background is covering the text under the pin. This makes it difficult to read the document when multiple pins are present. Example: => "wi??n"   You can click "Hide Pins", but this hides all of the non-active pins, but not the one you are trying to read at the time.   Please make the white background of the pushpin transparent or allow me to update the pushpin graphic file on the server to include transparent background. ... View more

We're human.  We make mistakes.  And some of us are fastidious.  I hate seeing files which were wrongly uploaded or obsolete in my list of files to review.  Also, most of us like to be efficient.  We don't want to have to delete our whole uploaded file list just to clean up a few files.  We should be allowed to delete individual review uploads.  You have a nice tool, but it is frustrating not to be able to do so. ... View more

Hi, the authentication via LDAP is a nice feature to organize the user registration in a world-wide environment by use of several AD groups that can be administered business-unit-specific. Unfortunately the user is not known in Collaborator until his/her first log in. This results in three steps: 1. Adding to AD group 2. User must log in 3. Project admin can add user to group Each step results in a latency and communication overhead between the admin and the user. It would be great to have a button in Collaborator's user management panel like "sync with configured AD group xy" (similar to RTC for example). ... View more

Would be great if the code collaborator was supplied in a Docker container with configuration options to trivialize the spin up of a new instance and the upgrade to a new server version. ... View more

I want to be able to edit or completely delete (with no trace) comments and defects I have added.   Strikout is not a good alternative; it wastes everyone's time to look at something that should have been deleted. The ability to edit or cleanly delete previously entered text is near-universal in systems that store user-entered text, and there are many good reasons for this.   In addition to those universally applicable reasons, the CC interface makes it easy to attach a comment or defect to the wrong line,. Further, the basic model of file-at-a-time reviewing with no global search or symbol lookup makes it difficult to review large or multi-file changes. When reviewing such changes, I often make comments that become moot when later functions or files are examined. I'm then reduced to either entering a later "never mind" comment (strikeout is only a slight improvement, because most authors are still going to waste time reding it) and/or effectively implementing my own "undo" by keeping all my comments and defects in a separate text file until I'm completely done, then going back in a second pass and actually entering them.  ... View more

Collaborator (and all Web-based tools, really) should retire any use of Adobe Flash.  The same functionality is now available natively in standards-compliant HTML5 browsers, which are commonplace at this time.     Flash Player is a never-ending source of security issues, causes grief for IT administrators, and is constantly pining for updates.  If it weren't for Collaborator, I could remove the flash plugin from my system entirely and enjoy improved security.       ... View more

Could you add multiple selection of Checklist Templates for a Review Template? (Example: In Collaborator, multiple custom fields can be choosen in a review template.) ... View more

I guess there is a way to pull it from the API, but that is messy.  We have Participant Custom Fields that we use, and want to get the information filled in those fields (or not) per participant in the reviews.   ... View more

Submitted on behalf of Avinash Ravikumar (Wipro Limited). ... View more

In many (or most) cases our users want to include cell formatting when reviewing Excel spreadsheets, because they become fairly unreadable with the formatting stripped out in the diff viewer.    This limitation means that either:   The author has to format the spreadsheet nicely for printing and save as PDF or use print to review, which can be a lot of effort, particularly when there are multiple sheets. The reviewer has to download the file in Excel, and go back and forth between Excel and the collaborator web page to log comments.  Because the Excel sheet is unformatted, and it's extra work to find the specific cell, the comments will tend to be logged in the 'general chat' area of the review. ... View more

In our daily code reviewing workflows people keep relying on the chat to clarify whether or not changes that were made to a certain file have been reverted. By that I mean, a file in the code base has been changed earlier in the review, then it was reverted to its original version. This means it disappears from the svn diff that is uploaded to Collaborator. In the Collaborator UI the reverted file then still shows up and it is unclear whether the changes to it were undone.   It would be great, if the status of a file in review that has been reverted to its original version could be indicated clearly in the UI, especially in the file view, not just the summary page.   It seems like a minor thing, but reverting of files happens quite often and it would be nice if Collaborator would support clear communication about this.   ... View more

If I write a comment on a review and later want to delete it, I click the Delete button to do so. The message which then appears looks like the image below:     So I have to click Confirm if I want to cancel, and Cancel if I want to cancel the cancellation; i.e. I don't want to cancel the comment. I think.   I think it would be a lot clearer if it used the word "Delete" instead of "Cancel", so could say "Are you sure you want to delete this comment?", and had Yes/No buttons, such that Yes deletes the comment, and No doesn't. ... View more

In the role template, I encountered some problems. Cases: 1- When choose No to "Allowed to modify review General Information", the role that assigned No, could not change checklist part.  2- When choose Yes to "Allowed to modify review General Information", the role can change Review Template, group, participant.   Could you separate the permissions of General Information as "Allowed to modify Checklists", "Allowed to modify Review Information" and "Allowed to modify Participant"? ... View more