This would be very useful for larger reviews where there are certain files (a subset) of the review which a particular reviewer must review, but may not care about others.

For instance a common change throughout the code base that must be made at once in multiple components. Authors can specify component owner's review their files only. Check boxes or other mechanism would be ideal. This also allows reviewers to "finish" their review without having to review all files and comments.

Adding a counter in the file view would be helpful a couple reasons. It would help with navigation for a heavily changed file. The reviewer would know where in the file they are, and how much they have left.

A feature could also be added which remembers this as long as the user is hitting the "next" navigation button Code Collaborator could bring them back to where they left off next time they open the same file. This would be useful for longer reviews when the current file is not reviewed in one sitting.

Instead of displaying long URL's it would be nice to use hypertext to shorten the link.

Currently using the RTC plugin, you can create a review before you submit the review, or you can make it happen on a specific state change.

I work in on a large team where people use different ways of doing code reviews, and hence not everybody wants a collaborator review done on a particular state change. Moreover, not every issue needs review. Some defects are hairy and require a review, while others ore a simple css change and so you don't bother.

I'd like to be able to selectively create a review, even after the code has been submitted.

Implement add versions for CCRC files

It should still be possible to move the line number before the comment is submitted through some user action, but it would have to be an intentional action (i.e. click the anchor icon to have a line drawn through the anchor icon to indicate you can now relocate the comment) vs. just clicking another line which can happen accidentally. Once the line number has been changed then the comment would automatically be anchored to the new location, unless the user repeats the step to move the line number.

Provide an HTTP REST API so we can easily data-mine Code Collaborator to get data, reports and statistics for display on our intranet site.

To extend the idea of customizable workflows, a per template setting to enable or disable review/file subscriptions could be useful.

The idea is to create an informal review template that does not include all subscribers to a review when only a couple of reviewers are needed.

No matter how hard the CodeCollaborator plug-in tries, it will always play catch-up with all the source control plug-ins available in terms of diffing. Take for instance Egit: CodeCollaborator did not even start the race yet! http://feedback.codecollab.com/forums/4652-code-collaborator-features/suggestions/259657-integrate-the-eclipse-plugin-with-egit

Unlike its plug-in sibling, command-line "ccollab" understood very well that it cannot win this diff race every time on every track. That is it provides the command "ccollab adddiffs". Please provide the same "adddiffs" feature in the plug-in.

Note the web interface has the same limitation:
http://feedback.codecollab.com/forums/4652-code-collaborator-features/suggestions/96280-upload-diffs-directly-via-the-web-client

Support for ClearCase Visual Studio plugin, same as the eclipse one

Code Collaborator shall be able to label to each file with the review # in SCM once review is marked done.

Allow to undelete comments (after hitting the red X by accident).

Add a link to the participants section of a review to add a random user as a reviewer. We want to encourage more knowledge sharing among our team. A step further would be an admin option to automatically add a random reviewer to every review.

Allow performing reviews from within DataStage.

When I have action items in a big review, the only way to get to the first action item, and the next one after that, is simply to scroll down the page until I see the yellow balloons. It would be very convenient, especially for big reviews, if there was a simple action that would scroll the page to the next yellow balloon.

Currently my team uses Komodo Edit and IDE and our Company would like us all to use Code Collaborator. I would switch to Eclipse, but it scares some of the notepad people.

Some support for mercurial has been added here: http://feedback.codecollab.com/forums/4652-code-collaborator-features/suggestions/37677-add-support-for-mercurial-hg-?ref=title

But post-commit support, which can include information about the revision under review, would be nice. :)

SmartBears: See Case 59102.