Microsoft Sensitivity Labels block uploads
My organization has started mandating Microsoft 365 document sensitivity labels. Learn about sensitivity labels | Microsoft Learn This creates upload errors when trying to upload documents with labels to Collaborator 15.0.15002. In the "load_fail" image, you can see the "Uploaded Files" tab with an infinite spinning 'location' field. In the "view_fail" image, you can see blank screens for the document view, and the comment field fails to apply comments as well. This is likely to end our ability to use collaborator as a review tool (primarily for certification checklist usage). There is unfortunately not much code review work to maintain this tool. Do you have any work arounds or possibilities for updates? Thank you for any advise, Neal
[Code Review] Error initializing changed files
Hi everyone, I encounter an error initializing issue which reason is that you have removed one or more files from workspace without notifying Subversion. The collaborator asks to resolve the workspace inconsistencies then try again. Server and client version are both v14.3.14303. For some reasons, I need to rename a file which had been uploaded to Subversion when I finished review process by SmartBear last time. However, the SmartBear Collaborator thought that my workspace is inconsistent with that on Subversion because of renamed files (old named file is removed and new one is added). Are there any ways to avoid the issue other than removing the file on Subversion first? Thanks a lot in advance.Code review created from Gitlab merge request is often being cancelled upon merging of the branch
We are using the Collaborator 14.2.14205 services in our company. The services were upgraded a couple of months ago from a much earlier version of Collaborator (11.5). Unfortunately we are not admins, and so our visibility is limited. Our workflow relies heavily on the Gitlab integration, where we use the merge request workflow to generate Collaborator reviews. Unfortunately, we have found that quite often upon merging the branch associated with the merge request, the corresponding code review is cancelled. Our IT support has shared snippets of logs with us that indicate that the code review is being cancelled due to the merge request being closed. We are not, however, explicitly closing the merge request - we are simply merging the branch. If anyone has encountered this, and could share a solution, it would be much appreciated. Are there service configuration settings somewhere that would affect how Collaborator handles code reviews (created from Gitlab merge requests) upon merging of the branch.?
JSON request to get reviewers and reviewer responses
I am trying to figure out how to use the JSON API to return a list of reviewers and if they have approved the review. It seems that with the ReviewService.getParticipants command I can get a list of reviewer usernames, and with the ReviewService.getReviewSummary command I can get a lot of information about the review (this seems to only show which reviewers have approved or commented on each file, without username). However, I want to just get a list of reviewer usernames and whether they have approved or not of the entire review, not file by file. Is this possible? Or to get a list of files with defects? Thanks in advance!
