Contributions
Re: Code Collaborator SOAP Api to check for a review status
Hello, this is Greg from Collaborator support. We do not have any examples for review status, and our example is written in Java, but here it is in case it is at all helpful: http://codecollaborator.smartbear.com/docs/manual/8.0/index.html?web_services.html Regards, Greg3.7KViews0likes2CommentsRe: Uploading a Word document based on a template with custom fields defaults back to original values
Hello, this is Greg from Smartbear support. Is it possible for you to start a case and send the document in question to support@smartbear.com along with the issue as you described it above? It would be helpful to take a look at the document itself and what is happening. Regards, Greg598Views0likes0CommentsRe: With the GUI client, how to uploaded the files that have already been checked in?
Hello, You are able to upload both pre and post commit changelists for ClearCase using our gui client. Here is our documentation on the matter: http://codecollaborator.smartbear.com/docs/manual/8.0/index.html?clearcase_ccollabgui.html Regards, Greg792Views0likes0CommentsRe: TFS credentials JAVA errors with Collaborator 8
Hello, this is Greg from Collaborator Support. We were just made aware of this issue. We redid the TFS integration to support additional features, and the fix for this is currently unreleased. Could you send an email to support@smartbear.com about this issue and I will see if we can help you by getting a private build or telling you how to alter your client so this will work. Regards, Greg952Views0likes0CommentsRe: Recent git changes in Code Collaborator
Hello, Here is a list of the major differences between 6.5 and 7.3 in git: 1: Binary files are now uploaded to reviews when using 'addgitdiffs', any changes to them were previously ignored. 2: Git now has addchangelist functionality from the server and the client and the web gui. 3: Submodule changes are no longer added when adding changelists and diffs from the master module 4: Minimum git version required is now 1.7 Regards, Greg W.776Views0likes0CommentsRe: Not able to upload files in p4, getting below error
Hello, It appears that we do not have permission to edit the directory, so we are not able to save any client side information. This directory is where we store things such as what server you are currently pointing at, so we need to have read/write permissions to it at all times. Also I notice that the error you pasted into the comment is from late July, there are more recent errors occurring the 4th of October. Did you copy the wrong error or are you seeing this behavior again? Regards, Greg W.827Views0likes0CommentsRe: CodeCollab integration with Subversion Problem
Hello, this is Greg from CodeCollaborator Support. It would help if we could get a debugging log of this failing. To do this, just put '--debug' after ccollab when running the command. This will create a log file in the current working directory, please send that file with a reference to this thread to support@smartbear.com and we will take a look and see what we can find. Regards, Greg W.1.2KViews0likes0CommentsRe: Handling "Orphaned" Reviews
Hello, this is Greg from CodeCollaborator Support. For ease of reading, I am just going to inline the answers. Is there a way to systematically trigger the review to be "Expired - Partially Reviewed" and sent to the next step in the workflow? There is not a way to do this without changing the user's role to one that a review does not wait on or removing the user. Is there a way to change the filtering of the "Incoming" reviews to suppress reviews that are a certain amount of time past their review due date? We do not currently have a way to change the sorting order of reviews. The sorting feature puts the oldest reviews at the top, since those are usually the ones who are past a deadline or have been waiting the longest. How do other groups handle this type of housekeeping function without having to staff "review enforcers" that chase down folks and force them to complete the review even though the value of their input is no longer timely? Some other workflows use triggers so that code cannot be pushed until a review is completed, which generally makes devs hurry along so they can get the code into the main trunk. Others generally push on reviewers long/hard enough until reviewing becomes part of the general workflow a dev goes through. Smaller reviews over larger reviews generally help, as a person is much more likely to sit and review something that is a 10-20 minute read to finish over something that would take hours however large reviews are sometimes unavoidable. Regards, Greg W.586Views0likes0CommentsRe: Unable to start review on changelists with files moved between folders
Hello, this is Greg from CodeCollaborator Support. In order to help diagnose the problem, we are going to need a debug log of this occurring. Could you please add the flag '--debug' after ccollab? This will create a log in the current working directory. Please then send the log to support@smartbear.com while referencing this thread. Regards, Greg Wyne573Views0likes0Comments