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.
Accessing internalCustomFields for Triggers in Collaborator
Hello world, I can use the http://collaborator.server/services/json/v1 API with the following JSON body to get data about a review. [ { "command" : "ReviewService.findReviewById", "args" : { "reviewId" : "42" } }] Specifically, it includes the following internalCustomFields key: "internalCustomFields" : [ { "name" : "JiraIssueId", "value" : [ "10600" ] }, { "name" : "ExternalTaskId", "value" : [ "" ] } ] I would like to use this JiraIssueId field for a review as an argument to one of the configurable Triggers (say Review Phase Changed for example). Does anyone know how I would access this internal field? I know I can use ${review.custom.foo} for visible custom fields that I create, but the internal custom fields are not documented in the http://collaborator.server/manual/index.html?admin_var_subst.html documentation. I've tried ${review.internal.JiraIssueId}, ${review.internalCustomFields.JiraIssueId}, and ${review.custom.JiraIssueId} but none of them work (giving me the following error) Error: Invalid input: Parameters: ${review.internalCustom.JiraIssueId} is not a valid substitution keyword Thanks for any help! Best, ~Chris
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.
