Configuration for a multi-server environment
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.
More Granular access controls for Subscription settings
The Subscription settings currently have only two parts, one specifying who can change them when someone is automatically added, and one specifying who can modify subscriptions. The Subscription settings are configured on each user account as to what they want to be automatically subscribed to. The setting related to who can modify those is either "Administrator", meaning only an administrator can modify any subscription settings for what users are subscribed to, or "User" meaning all users can modify their own subscription settings. Most of our users are not trusted enough to modify their own subscription settings, so we're currently using "Administrator" for the restriction, but we have a collection of Senior Developers and Project Leads that need/want to be subscribed to a number of different things and are trusted enough to modify their own subscription settings. The only solution is to currently make those trusted users Administrators, or to have one of the existing Administrators modify the user's settings whenever they need/want to change their subscriptions.
AWS Code Commit Support
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.
Allow anyone to re-open a closed review by clicking a link, NOT by adding a comment
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...
Allow "messages from the administrator" to be accepted and hidden to increase vertical space
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 bebeneficial. 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!
Support MariaDB on Linux
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.
