Add multiple pull requests to "Remote System Links"
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.Implement sync of GitHub pull request reviewers and Collaborator reviewers
Submitted on behalf of Debdas Mondal (HSBC). GitHub pull requests may have reviewers assigned to them. It should be possible to synchronize the list of pull request reviewers and the list of a linked Collaborator review's participants.
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.
Reviews of a submodule change need to show file change in review
When using a git submodule with a pull request / merge request mechanism enforced (i.e., Bitbucket), when the developer changes the submodule and there is no other change in the parent repository other than pointing to the new merge commit, Collaborator shows no files in the review. Commits are properly listed, but there are no changes to actually review, which is incorrect. Bitbucket, for example, lists the "pointer file" that holds the submodule commit reference. It would be extremely helpful to have Collaborator show this difference as well.
Change validation process in Collaborator client
This is what we run into if a user has 3 or more Collaborator configurations... When our users change their network password, once they open the Collaborator client (which has their old network password in their ClearCase configurations), it immediately locks their network account which then throws a validation error in Collaborator. It would be better if you didn't have Collaborator auto validating upon open so that users have the chance to either remove these configurations, or edit them to change the password. Also, I think it would be better to have a single place for the user credentials instead of in each configuration. That way the user would only have to change it in one place.Look at the history of a file when an SVN add occurs
Is there a way for Collaborator to look at the history of a file when an SVN add occurs? Right now, with TortoiseSVN, most of the time an SVN mv is done as an SVN rm and SVN add. As a result, when we set up a review that contains a file that this has been done to, Collaborator shows the file as being deleted and then as a completely new file, so that we cannot see the changes that actually occurred in the source code.
SVN import failed as a result of file merging
Since Collaborator uses the Subversion command-line client and its native commands to fetch the data from the local SVN repository or the SVN server, Collaborator will abort the entire uploading process if at least one of the outputs of the native commands will be unexpected or contain an error. This is done to prevent losing data or uploading the incorrect files to the Collaborator server. It would be good if CodeCollaborator would be able to handle importing a review from which a file has been removed during a merge to handle this differently. i.e:continue to import the files it could parse, and maybe put up a warning or something, rather than aborting the import.Log all activities of users and admins in Collaborator
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.Add Perforce integration to Collaborator Visual Studio plugin
Submitting a feature request on behalf of Symantec Corp: There is no possibility to add a Perforce SCM repository in Collaborator Visual Studio plugin at this moment. The idea is to add Perforce SCM support to Collaborator Visual Studio plugin to make it possible.
