Forgot to add Log info:
Tail of log:
!ENTRY com.smartbear.collaborator.ui 4 0 2016-09-15 14:13:44.251
!MESSAGE Could not finish Review Job
!STACK 0
com.smartbear.ccollab.client.CollabClientInvalidInputException: Errors found:
[ {
　 "result" : { }
}, {
　 "result" : { }
}, {
　 "errors" : [ {
　　　 "code" : "AccessError",
　　　 "message" : "Cannot upload changelists to a review unless you are a participant or administrator, due to review access restrictions in place."
　 } ]
} ]
　　　　　　　　　　　　　　　 at com.smartbear.ccollab.client.commands.Command.sendBatch(Command.java:562)
　　　　　　　　　　　　　　　 at com.smartbear.ccollab.client.commands.AbstractAddChangelistCommand.executeJson(AbstractAddChangelistCommand.java:233)
　　　　　　　　　　　　　　　 at com.smartbear.ccollab.client.commands.admin.review.AbstractReviewCommand.executeJson(AbstractReviewCommand.java:208)
　　　　　　　　　　　　　　　 at com.smartbear.ccollab.client.commands.Command.validateAndExecute(Command.java:414)
　　　　　　　　　　　　　　　 at com.smartbear.collaborator.Collaborator.executeJson(Collaborator.java:243)
　　　　　　　　　　　　　　　 at com.smartbear.collaborator.jobs.AddToReviewJob.processChanges(AddToReviewJob.java:209)
　　　　　　　　　　　　　　　 at com.smartbear.collaborator.jobs.AddToReviewJob.run(AddToReviewJob.java:132)
　　　　　　　　　　　　　　　 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Sue
Hi Sue,
Unfortunately, you have faced a known issue (COLLAB-1407). If the "Restrict access" option is set to one of the highest restriction options (participant or group), the GUI client with JSON API default option runs into the "Cannot upload changelist to a review unless you are a participant " issues. Our R&D team is aware of this problem and will try to fix it in one of the future releases.
As a temporary workaround, you can downgrade the client to the previous 9.0.9001 version that uses legacy api as the default option. You can download it using the link below:
https://support.smartbear.com/downloads/collaborator/all-installers/
Also, you can create a review using the Web UI, specify the review information and add necessary participants, and upload the changelist to the newly created review using the GUI client. You will be a participant of that review and this issue won't occur anymore.
