Option to not re-open review after comment
Hello, is there a way (admin option?) to not re-open a review after it's been completed, if someone puts a comment after the fact? Often times, the reviewer has already approved a review, and some other observer will put a comment to ask a question or propose a future modification. It would be nice for the author to be notified that such a comment has been added to the review. But right now this action will put the review from "completed" to back in "inspection". Meaning everyone is notified and all the reviewers will have to approve the review again!! that is the most annoying flow ever. Is there a way to disable that feature? I haven't found the option in the documentation. thanks, JMTHow to get Azure Boards work item info for recent GitHub PRs in a given repo?
have Git repos in GitHub and work items in Azure DevOps (Azure Boards). We are using the "Azure Boards" GitHub app, and thus when we addto a PR comment, it links to the right work item in Azure DevOps? We would like to create a list of recent GitHub pull requests that show the Azure Boards work item that is associatedand its parent work item. We could do this when our PRs were in Azure DevOps Git, but it seems tough to do so with PRs ion GitHub.
Create System Message from JSON API
Hello, Is there a possibility to add a comment to review to be displayed as System Message? Currently I use the ReviewService.createReviewComment method but is displayed in the User Messages section from review chat. Why we need this? To add comments from triggers side as automated process validation. [ { "command": "SessionService.authenticate", "args": { "login": "{{collab_dev_admin_user}}", "ticket": "{{collab_dev_admin_token}}" } }, { "command": "ReviewService.createReviewComment", "args": { "reviewId" : {{collab_dev_reviewID}}, "comment" : "This is a System message", } } ] Thank you for support.
Perforce ensure review completed
I seem to be having some trouble getting a script to ensure a review was completed to work. I don’t seem to get any kind of status from ccollab.exe. I used this command: C:\CollaboratorClient\ccollab.exe --url http://someurl:8080/ --scm Perforce --p4port {Perforceserver} --p4client CollabTrigger --p4user {p4user ID} --p4passwd {password} admin trigger ensure-reviewed 175817 The status always seems to be empty when going through the perforce trigger and I can submit anything. If I try the above command manually I get: ERROR: SCM system communication problem: This trigger must be configured as change-content. Contact your Perforce administrator to perform the change. I have the Perforce trigger as follows: p4collab change-content //depot/P4validation/... "perl %//Scripts/p4_collab.pl% %serverhost% %changelist% %client%" I’ve tried to find the renumbering script that is linked on this page to see if that is my problem. https://support.smartbear.com/collaborator/docs/source-control/perforce.html Perforce version 2015.1 Collab version 11.4 I'm probably missing something easy so any help is appreciated. ~jeff
create-review post commit hook - password management and participants
Hello Is there any tutorial on how to get this working in a production environment? Especially useful would be some hints on how: 1. the hook should manage the required passwords ( ccollab-admin-trigger-create-review) (we use LDAP). 2.we can control the participants of the review (ie. like a per-user or per-source branch template?I imagine this could be done with some "custom scripting" but since it's probably a very popularrequest is there some built-in support or best practice?)
