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

We need to restrict all users from creating new projects in collaborator web application because it should allowed only for system administrator.  ... View more

OIDC is much simpler to set up than SAML and having support for other OIDC providers besides GitHub and Atlassian would be beneficial. Enterprises that have their own internal OIDC provider and don't (or cannot) use GitHub or Atlassian Crowd would benefit from a simpler A&A configuration.   ... 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

Currently once you have typed a comment you have to use the mouse to click Add.   Ctrl+Enter should add the comment like in many other applications. ... View more

Requesting a setting for administrators to set to logout (and free floating licenses) after a set time of inactivity, ex. 1 hour.   My users have the behavior to open their browser to login to CC but unfortuanetlly don't close the tab, nor do they logout of the server, what hinders other users to not be able to receive a new license.   This is very important for our company. ... View more

I would like to see support for reviewing local HTML documents, where I can navigate, drop pins and see differences from within the Collaborator environment. Something related has already been done with the Simulink review tool. ... View more

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

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

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

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

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

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

In collaborator it would be nice to be able to have emojis in the comments. ... View more

In larger reviews, there are sometimes many chat windows. As the review progresses, sometime chats are "done", in that there is nothing more to discuss. These chats now polute the general chat space, and the "accepted" icon is removed if the author uploads another file (often causing the reviewer to look at old chats). Please add an ability to "close" a chat, where the "accepted" icon is kept on that chat line. Perhaps even the (sometimes long) chat bubble could be minimized once closed.. ... View more

Many of the users of the Collaborator application in my company want to use it to review changes made to Microsoft Word documents. However, the document Diff Viewer provided with Collaborator does not have the ability to "understand" the word documents in a their native format - as it first converts them to text files and then displays them as PDF files.  Thus, the "context" of the changes is lost.    For instance, users would like to be able to ignore differences in versions of word documents caused by mere changes to document Header and Footer page numbers, for instance. This type of filtering is not provided by Collaborator's diff viewer, since it treats all differences between 2 Microsoft word documents the same (as basic text), whether they come from differences in body text, header text, footer text, table of contents text, etc.    Also, is there a way for Collaborator to see/create something similar to the "Document Map" that is provided in Microsoft word - this would simplify document navigation because then section numbers of the document could be navigated to directly. Also, if the section numbering, header, footers, body text, TOC of the document provided in the open xml format (namely the docx file) were parsed by Collaborator's Diff Viewer, and some functionality created to allow the Diff Viewer to potentially ignore changes in files caused by updates to Table of Contents, Header, Footer text, etc.  Currently, this type of filtering of word document changes is not possible in Collaborator's file Diff Viewer.  It would be nice if add-ins could be provided that would provide this type of functionality. ... View more

I would love to have collaborator integrated into VSCode. The Visual Studio .vsix doesn't install in VSCode 😞 ... View more

On the "Diff" screen when viewing the changes for a file, show its full (relative) path, not just its base name at the top of the screen. Sometimes we could have files with the same base name in different directories, or just want to verify the path of a file we're viewing the diff for. This could perhaps be a user setting. ... View more