Git Repository Name on review with multiple git repository.
When you add several changes from git via GUI client to one review there is no way to understand which repository the file belongs to. For example(screen in attache), if several commits contain files with the same name, you can only understand which repository they refer to using a hash. The screenshot shows an example when all 3 files with the same name refer to different repositories. Adding the name of the repository, and not just the file with changes, would help us a lot. Thanks for attention!
document compare
I often find most of the changes are boilerplate changes, typically the date and/or document revision number in the footer. This means “jump to next change” is not particularly helpful since it takes me through each footer of every page. I know it will be non-trivial, but it would be amazing if there would be a way to skip this sort of boilerplate change that changes on every revision and isn’t really a change.
Add a "Ready for Approval" state to defects
It would be helpful if there was a third state to indicate that a defect has been resolved, but still needs to be "approved" (marked Fixed) by the author of the defect.Currently a defect only appears as "Open" or "Fixed" in the Defect Log. It is difficult to tell which defects have been resolved without looking through the comments, or having someone tell you to look at a specific defect. When there are a lot of defects in the Defect Log, a third state to filter on would make it easy to identify those defects that need to be marked Fixed. Maybe this could also be shown with a different color bug, instead of red or green.
Reference the Line of Another File in the Same Review
In the chat box of file foo.cc I would like to reference a specific line in file bar.cc.For example, I have bar.cc:line 12 written in my code collab chat box. In this case, code-collab only recognizes and allows the jump to bar.cc, but not to the line. I would like a featurewhere a designer canwrite a reference to line 12 in bar.cc and Collaborator automatically auto-links the to the correct line.Add sort functionality to client GUI
It would be great if the Collaborator Client allowed sorting of the "SCM Configurations" grid. We have 70+ projects and the default order makes it rather difficult to find a single project without scanning through the entire list. An alpha sort on the 'Local Path' column is what we would use, but I support sorting on any of the columns would make sense.
Allow Admins to close reviews
Bringing back an old thread - I'd like anyone with Admin privileges to be able to move a review to Completed. We've had several instances where someone has left the company, or is on extended leave, and their roles is required to move a review to completed. On solution is to shuffle roles - while that will allow a review to close, it's "not right". If the author of a document is out sick - yes I can assign the author role to someone else - but now you are fudging the review records in order to get the closure. Later when an auditor comes in we have to give a song and dance as to why the roles in the review don't represent the actual roles the staff members have. We shouldn't need to alter the records to move things forward. The review is more than a record of defects - it's a record of who did what, and we shouldn't need to compromise that to get around a technical glitch.
Make excluding many files from a review easier
Rather than having to click on each file to exclude it would be good if we could exclude content by folder, by file filter, by holding down the shift key and selecting 15 files at once. Things that allow working with and excluding large lists of files easier and less time consuming to ensure just the essential files are included in any review. Not much thought or effort has been put into the current mechanism.Change validation process in Collaborator client
This is what we run into if a user has 3 or more Collaborator configurations... When our users change their network password, once they open the Collaborator client (which has their old network password in their ClearCase configurations), it immediately locks their network account which then throws a validation error in Collaborator. It would be better if you didn't have Collaborator auto validating upon open so that users have the chance to either remove these configurations, or edit them to change the password. Also, I think it would be better to have a single place for the user credentials instead of in each configuration. That way the user would only have to change it in one place.
Allow ignoring of only leading whitespace
When reviewing code using CodeCollaborator, there is an option to ignore whitespace in the diffs. This is not-fine-grained enough. Frequently I might want to ignoreleadingwhitespace if the code has been indented differently, while still catching other whitespace changes. Please add an option to ignore only leading whitespace.
