Collaborator Feature Requests

  I often find most of the changes are boilerplate changes, typically the date and/or document revision number in the footer. This means “jump to next change” is not particularly helpful since it takes me through each footer of every page. I know it will be non-trivial, but it would be amazing if there would be a way to skip this sort of boilerplate change that changes on every revision and isn’t really a change. ... View more

Bringing back an old thread - I'd like anyone with Admin privileges to be able to move a review to Completed.   We've had several instances where someone has left the company, or is on extended leave, and their roles is required to move a review to completed.   On solution is to shuffle roles - while that will allow a review to close, it's "not right".   If the author of a document is out sick - yes I can assign the author role to someone else - but now you are fudging the review records in order to get the closure.   Later when an auditor comes in we have to give a song and dance as to why the roles in the review don't represent the actual roles the staff members have.   We shouldn't need to alter the records to move things forward.      The review is more than a record of defects - it's a record of who did what, and we shouldn't need to compromise that to get around a technical glitch.    ... View more

Rather than having to click on each file to exclude it would be good if we could exclude content by folder, by file filter, by holding down the shift key and selecting 15 files at once. Things that allow working with and excluding large lists of files easier and less time consuming to ensure just the essential files are included in any review. Not much thought or effort has been put into the current mechanism. ... 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 add several changes from git via GUI client to one review there is no way to understand which repository the file belongs to. For example(screen in attache), if several commits contain files with the same name, you can only understand which repository they refer to using a hash. The screenshot shows an example when all 3 files with the same name refer to different repositories. Adding the name of the repository, and not just the file with changes, would help us a lot. Thanks for attention! ... View more

We use the "Message from the administrator" feature to show important information to users about the type of data they can use Collaborator for, however in v11.3.11301 the message is always present at the top of the screen.  There is no way for a user to hide the message and it consumes valuable screen real-estate.  Many of our users review portrait format documents on landscape screens and so being able to hide or move anything that prevents the use of the full vertical size of the monitor would be beneficial.   Please provide an option for users to be able to read, accept and hide the message upon each login.  Better still, provide an option to do that and also to hide/move/shrink the horizontal menu bars.   Thanks! ... View more

In a Large enterprise there will be multiple admins. To track who has done what, Admin should be able to get the log of all users activities. Like, Disabling and Enabling review templates, Disabling and enabling users or adding users etc. In simple terms a log should be generated for every activity happens in Collaborator through all the ways. ex: GUI, API, Collab client, Thirdpart clients, Commands etc.   ... View more

Problem: I upload changes as a commit range in git between a reference branch (master) and my current HEAD.  I then later need to rebase my current HEAD against an updated reference branch (master) and re-upload the changes.  It cannot be differentiated in the file version selector during a review which versions of the file are reference branch (master) and which are HEAD versions. Generically, client tool uploaded differences from git commit ranges automatically label all versions of files as seen in file version selector drop down, with check-in time and non-human readable git object hash (not commit hash) only.  Rebasing changes against the latest version of the reference branch, or merging the latest version of the reference branch into the changes, between a first and second upload to a review causes the "before" version from the reference branch to be different during the second uploaded of files and have a newer timestamp than the "after" version of the file from the first upload.  The "before" versions therefore can't be differentiated from the "after" versions in the drop down.   Solution: Add optional command line argument for "addgitdiffs" that will allow user specified names to be added to the before and after versions of all files included in the commit range. Conflicting names are automatically appended with standard "(1)", "(2)", etc for a given file based on upload order.   For example, if I have changes on a "work" branch that originally forked from "master" branch and changed fileA and fileB, my upload command would be ccollab addgitdiffs --before-name="master" --after-name="work" ask master...work which would upload all changes made on the work branch since it split from master by uploading fileA and fileB from the commit on the master branch right before the work branch split, and fileA and fileB from the head of the work branch (currently).  The extra arguments would add labeling for all the files from master as "master" and those coming from the work branch as "work" (new). When my review continues for a while and I need to rebase my work branch against the since-updated master branch I'll need to re-upload my changes relative to the new reference point on the master branch.  Running the same command as before accomplishes that but causes a problem. When the differences in fileA are viewed without this feature, what's seen in the file version selector drop down is (larger numbers with the timestamps indicate newer timestamps): "<git object hash> <commit timestamp 1>" <---- from master branch in first upload "<git object hash> <commit timestamp 2>" <---- from work branch in first upload "<git object hash> <commit timestamp 3>" <---- from master branch in second upload "<git object hash> <commit timestamp 4>" <---- from work branch in second upload   With the recommended feature this list becomes much more clear: "master    <git object hash> <commit timestamp 1>" <---- from master branch in first upload "work      <git object hash> <commit timestamp 2>" <---- from work branch in first upload "master(1) <git object hash> <commit timestamp 3>" <---- from master branch in second upload "work(1)   <git object hash> <commit timestamp 4>" <---- from work branch in second upload     ... View more

We have developed an integration from a document-management system that uses one review custom field to store foreign document id and version information. When the review is created this information is provided from the other system through the JSON API. Obviously we do not want the GUI Client users to change this field, but currently Collaborator does not allow this. To make life easier in this kind of use cases, I propose Collaborator admin section to have following extra (boolean) settings for review custom fields: hidden, only to be modified/read through the API read-only, visible in GUI, but modifiable only through the API ... 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

It would be great if the Collaborator Client allowed sorting of the "SCM Configurations" grid.     We have 70+ projects and the default order makes it rather difficult to find a single project without scanning through the entire list.  An alpha sort on the 'Local Path' column is what we would use, but I support sorting on any of the columns would make sense. ... View more

This is what we run into if a user has 3 or more Collaborator configurations... When our users change their network password, once they open the Collaborator client (which has their old network password in their ClearCase configurations), it immediately locks their network account which then throws a validation error in Collaborator.   It would be better if you didn't have Collaborator auto validating upon open so that users have the chance to either remove these configurations, or edit them to change the password.   Also, I think it would be better to have a single place for the user credentials instead of in each configuration. That way the user would only have to change it in one place.  ... View more

When reviewing code using CodeCollaborator, there is an option to ignore whitespace in the diffs. This is not-fine-grained enough.   Frequently I might want to ignore leading whitespace if the code has been indented differently, while still catching other whitespace changes.   Please add an option to ignore only leading whitespace. ... View more

If a file in a review is new to source control, it doesn't open the diff window, it just opens the file by itself.  While you add add defects to particular lines, there's no way to add an overall comment / defect. ... View more

In the VS extension, you can right click a line an add a comment or defect, but then you can't edit or delete it if you need to, that requires going to the web UI to do so. ... View more

In the VS extension, when preforming a review, every time I click a file name to see the changes, it causes the Review window to scroll back to the top, so that when I close the diff I have to scroll back down to the next file. ... View more

We have a large number of users who would benefit greatly from syntax highlighting for Robot Framework code. We have cobbled together something on our own, but would very much appreciate if you could add this feature in the long term. ... View more

Do you any plan to support Multi Factor Authentication in the upcoming releases? ... View more

In the Collaborator Enterprise Client GUI, click “Add Subversion Diffs”. Click the “Revisions” tab. Change the Subversion URL to be the top level of the directory structure you want to diff. The “Before Revision” should be the last SVN commit that was reviewed (see SVN’s “Show Log” for the revision ID).   However, at this point, you cannot chose to include/exclude some files from some of the revisions. This is useful when certain things should be submitted to the repository but not reviewed (*.bin files for instance). This would be a nice feature. ... View more