I've been evaluating the Code Collaborator 7.0 interface (7.0.7022). My company currently uses the older interace and we are determining if we can move on to the new version. I found a number of things in the new interface that I was unhappy with. Here is my list:
Code Collaborator overview screen
It is not clear how the reviews are sorted when the overview is first opened and once you sort on one of the columns there is no way to get back to that original sort order.
You cannot sort based on deadline date.
I've found that it doesn't always show the check-boxes for filtering the content of the review list. If the check-boxes aren't shown, then sorting by one of the columns causes them to appear.
Code Review overview screen
The way all of the comments and approvals have been compressed into a single column doesn't make sense to me. The use of a tooltip to provide this information is not as useful as the way it was previously where there was a column for each participant and you could easily scan the list of files to see who has been going over which parts of the review.
You are using symbols to represnet the state of a file (open circle for initial). I couldn't easily find a key to show me what all the different symbols mean. I think hiding this in the tooltip is not all that helpful. You could have just left the text "Initial" in the column.
If a participant is an observer or author that does not have the option to "Finish" a review, the Finish button is disabled and you have to hover over it to get the tooltip to understand why it is not an option. This is unclear because the text next to the button is telling me to approve the review as-is and has no indication why I cannot.
In the file review window
My biggest problem here is that the whole comment/defect area on the left-hand-side of the screen is very hard to understand now. It used to be very easy to distinguish between the sections which represented a line of code. In the new interface they seem to all blend together and it's very hard to read.
I didn't find the way for entering defects to be all that intuitive and I couldn't find how to mark a defect as external.
I found that in some cases, it forced me to use a label when creating a defect and in other cases I was able to leave it blank. I was unable to find the reason for the difference.
I have a defect custom field associated with my template, but it did not display that field when I entered a defect.