Contributions
Re: Collab 14.0.14002 : How to see what is blocking code review from getting Approval?
It is not usually the author who has the responsibility to move the review from INSPECTION to COMPLETED. It is usually the reviewers with that responsibility. When you hover over the "Send to Completed" button for each of the author and reviewers, what does the tooltip say? If you are in the INSPECTION phase are there are open defects, the button will say "Send to Rework". If there are no open defects, it will say "Send to Completed". Once all participants (*who are required to*) click on "Send to Completed", the review is done. See the documentation about the workflow in the review: https://support.smartbear.com/collaborator/docs/working-with/concepts/phases.html6Views0likes0CommentsRe: Collaborator 13.2 and 13.4 cannot login in the command line if the password contains a double-quote
This isn't a Collaborator problem . . . it is a Windows CMD shell problem. You will have a problem with other characters as well (like caret ^ and ampersand & and percent %). There doesn't seem to be a simple clean way to do this.2KViews0likes3CommentsRe: Collab "Cpu resources reduce" & "Version Upgrade" Problem
For the first issue, use your system monitoring tools to verify what is using the CPU. Is it all Collaborator? For the second issue, "upgrade your database" refers not to which version of the Oracle server or Oracle JDBC driver you're using but rather to the fact that we have to upgrade (modify) the Collaborator database schema to work with Collaborator 13.6. The upgrade error *might* be a temporary problem in the internal DB upgrade process. Try restarting Collaborator. If that doesn't work, then the problem may be that you need the CTX_DDL package installed on the Oracle server. See this article: https://support.smartbear.com/collaborator/docs/server/install/db/oracle.html If that doesn't help, open a support case.553Views0likes0Comments