Collaborator Feature Requests

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

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

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

Debian and Ubuntu Linux at least now ship MariaDB as the default instead of MySQL. I've recently installed v11.3 on Debian 9.5 (Stretch) with MariaDB v10.1 and it seems to work correctly, but it would be nice for the installation instructions to indicate that MariaDB is a supported database. ... 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

Users are complaining about this setting: Allow Reopening Completed Reviews Once a review has completed, should participants be allowed to re-open the review just by making an additional comment? If not allowed, an administrator is still able to re-open a review by clicking a link.   They want to be able to comment on a Closed review without Re-opening it, but also be able to Re-open reviews without an Administrator. One way would be to make the re-open link mentioned above available to all - maybe add a separate setting to enable that... ... View more

For environments that are larger and need some server redundancy, it would be nice to have a multi-server configuration available. The servers would be behind a load balancer of some sort and traffic would be divided between the two or more servers hosting the Collaborator application. ... View more

We would like to see if the collaborator can have integration with Redmine issue tracking system. While this was not our primary concern, but it would be really nice to see that the issue tracking and review system working hand in hand.   ... 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

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 to copy templates and role configurations instead of having to update all default settings. This would speed up our process of adding new groups when customizations are required.  ... View more

I am using Collaborator Enterprise 13.6 and trying to archive my nearly 1 TB of data in my Content Cache folder on my server.  We have tried to archive off to a separate network location (to free up space on my server) and it will not copy the files.  We have to do this the brute force method and archive to a location on the same server (small increments) then copy that archive to the other network location.  We will have to do this with each incremental archive.  Then they are not together, but they are still individual archives.  I would like to request that the ability to archive to another network location be added so that when an archive is done, the data is all together in one Content Cache folder, and I don't have to look through a bunch of separate archives to find the review I want to restore.   ... View more

as it is now, home screen fields that are added and ordered will reset to default.  The ability to have these personal preferences retained would be great. ... View more

currently the ability to re-open reviews is based upon the review templates. It would be better to have this setting be at (or included in) the limited admin level.  It is not typically a setting we desire everyone to have, but having a limited team (quality) be able to re-open is highly desirable.    ... 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