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

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 need to restrict all users from creating new projects in collaborator web application because it should allowed only for system administrator.  ... 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

1) Defects: List all defects associated with all the reviews in a project 2) Reports: Add a report to list all reviews for a project ... 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

Howdy,   Please add Code Collaborator support for AWS Code Commit repository integrations to the web client.   Example of this current functionality can be found here: https://support.smartbear.com/collaborator/docs/source-control/git.html https://support.smartbear.com/collaborator/docs/source-control/repo-hosting/index.html   In the same way that Github, Bitbucket, and Azure can easily be integrated to the Collaborator, I would like for this process to also function with AWS Code Commit Repos. I may currently use Code Collab and AWS Code Commit via the client gui and local changes, but I would also like to have direct repo integration like the hosted repos do.   Thanks. ... 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

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

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

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

I have a team working on Gitlab integration with Colalborator. When merge requests are made on the GIT side, a Collaborator review is automatically created. Unfortunately, the Group and Templateis selected somewhat randomly.    According to customer service they are "The last Group and Templated that the merge author happened to use".  Often this is the wrong choice.  WHen we change them by hand we then lose all the other auto filled data in the review.   Give how well the GIT / Collaborator integration is set up, it would be nice to have a way to specify Group and Template to use for the review.  ... 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

Submitted on behalf of Gadadhar Dalei (Wipro Limited).   Currently, Collaborator loads all users to the User List. If there are thousands of users, it may take considerable amount of time. ... View more