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, JMT
Rework what is "Action items"
Right now, I get an action item when a review moves to Inspection and I'm the inspector. That's fine, but once I send it to rework, I don't want to see it again until its back at Inspection. Right now though if the author uploads new reviews, it shows back in my Action item list. Likewise Inspectees will have their review show as an Action Item while its still in the Inspection phase. For larger reviews this is a problem because they'll start uploading new revisions while I'm still conducting the review. Both of these result in confusion for my team.How 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.
Not allowing removal of participants without confirmation
I would like to suggest that removing of names can't happen without a confirmation. This is especially true when the removal of the name will allow the review to be completed prematurely. If there was a confirmation screen that popped up that said "Are you sure you want to delete this person even if the review will complete at this time, and in order to re-open the review you will need the assistance of an admin?" We have had several recent examples where a participant was removed from the review before the replacement participant was added, and the review ended prematurely and had to be re-opened by an admin. The proper sequence would be to add the new participant before you delete the old participant. The review would not end in this sequence because the new participant would have to approve of the review before it completed. People do not know that they need to add before they delete. The confirmation screen would not prevent this from happening in all cases, but it is better than not knowing that they will cause problems if they delete first. We are open to other suggestions, if someone has a better way of avoiding the situation.