Contributions
Re: Visual Studio crashes
Hi, To help us investigate the error, please collect some additional information on it by following the steps below: 1. In Visual Studio, open the Options dialog (Tools | Options) from the main menu. 2. On the Collaborator | Logger page of the dialog, enable all the types of log messages to display and click OK. 3.In theOutput panel of VS, set the Show output from: option to Collaborator. 4. Reproduce the error. 5. If the Output panel exposes any messages related to the error, save the contents of the panel to a file. 6. Zip the contents of the <user home>/.smartbear/vsext folder to an archive. 7. Submit us all the collected files.436Views0likes0CommentsRe: Perforce ensure review completed
Hi jeff, As far as we can see, you've already resolved the obstacle you faced. In general, to troubleshoot trigger-related obstacles of any kind, add the --debug parameter to the ccollab command line and analyze the ccollab.log file generated on the Perforce server machine.793Views1like0CommentsRe: getReviewFile throwing null pointer exception
Hi Ben, The error occurs because your ReviewService.getReviewFile method call lacks of two required parameters. Please modify the method call like this to make it works: { "command" : "ReviewService.getReviewFile", "args" : { "versionId" : 123456, "reviewId" : 1234, "clientBuild" : 12203, "active" : true }}685Views0likes0CommentsRe: Collaborator users getting logged out due to Javascript error
Hi, The situation was originally caused by using an unsupported MySQL Connector/J 8.0 JDBC driver. To avoid the situation in general, a MySQL database for Collaborator needs to be configured exactly as described in the MySQL article.749Views0likes0CommentsRe: Tray Action Items window not closeable
Hi, This behavior is specific to the UI framework used by the Tray Notifier. The dialog box can be closed if you put the focus to the Actions Items list control within the dialog (not to the window itself) and press [Esc]. Our developers are considering to implement the possibility to close the window normally as well.753Views0likes0CommentsRe: about Total Person Time vs Total Reviewer Time
Hi schneid, Your assumption is correct. The Total Reviewer Time metric can explicitly be calculated by querying the activity table of Collaborator. In the table, each row represents a slice of time where the user was active. There can be many slices for a given user in a single review. Each slice includes duration (in seconds) and "start time" that is encoded both as database date/time (activity_startdate) and a number of seconds since 1970-01-01 00:00:00 GMT (activity_startsecs). The activity_code column of the table tells whether the user was acting in the capacity of an author (A), reviewer (R), or was doing rework (F) as opposed to actually reviewing. Also, there is a code for when someone views the review but is not a participant (P). Thus, the metric is a sum of all the durations of each reviewer activity (R) associated with a given review.677Views0likes0Comments