This topic describes the changes made to Collaborator 2.1.703. For information on the changes made to other versions of the product, see Version History.

  • added — New role-specific option to have participants not re-invited to a review when another user makes a comment

  • added — New role-specific option to control whether this role is allowed to change review details while the review is active (Case 34302)

  • added — Allowing edit of the review details after the review is complete, but only when you are a participant or admin (Case 31478)

  • added — Special warning when a user is viewing a review but is not a participant in that review (Case 34026)

  • added — Display the title of the current workflow in the Review Overview section (Case 33972)

  • added — Now supporting either ccollab set scm perforce or ccollab set scm p4 to configure ccollab Perforce settings.

  • fixed — Long comment text does not wrap in chat viewer. (Case 34289)

  • fixed — CMVC integration fails when not all fields are populated

  • fixed — Subversion was not properly handling file changes when parent directories were moved or deleted

  • fixed — Subversion was not properly handling file changes when the parent path was the result of a directory-move, as with the first check-in on a new branch

  • fixed — Some non-ASCII characters not displaying correctly when entered in the AJAX chat component in side-by-side view (Case 34050)

  • fixed — HTML characters in the review title cases Review Overview page to display incorrectly (Case 34281)

  • fixed — In ClearCase, ccollab addactivity picks wrong latest version when not checked out (Case 33771)

  • fixed — Email notifying a user that they have been added to a review did not include their role (Case 34165)

  • fixed — Reinstalling command-line client sets SCM configuration to Perforce when Perforce is installed, even if the user specifically switched to a different SCM system (Case 33741)

  • fixed — Confusing error message (UnknownHostException) printed to the console instead of a useful message (Case 33858)

See Also

Version History

Highlight search results