aleppke
-
187 votesplanned ·
AdminBrandon DuRette
(Admin, Code Collaborator)
responded
There are underlying technical reasons why this is tricky, so our standard answer is to just comment at the top of the block of code you are commenting on and preface with an indicator of the block that you are discussing. For example:
“This method could be…”
or
“This loop would be better if…”However, if there is overwhelming desire for this feature, it is something that we would consider adding.
aleppke
commented
·
I would like to see the standard multi-selection options (click and drag, ctrl+click, shirt+click). The comment/defect could then be shown on the side, lined up with the highest visible line its associated with. This would mean that the comment moves as the user scrolls so the comment is always visible provided one of the affected lines is visible.
aleppke
gave this 3 votes
·
-
50 votesaleppke
commented
·
This is the only area where Crucible + FishEye blows you guys out of the water. They make it extremely easy to upload revisions and files directly from the web browser. I'd say this area is the greatest weakness of Code Collaborator. I'm surprised more people haven't voted for it.
aleppke
gave this 3 votes
·
-
182 votescompleted ·
Adminebrown
(Admin, Code Collaborator)
responded
The Visual Studio addin is available in v6.0, and is no longer in beta. The current integration is only through the Solution Explorer. This feature is now closed. We will most likely be providing future integrations with source control plugins for Visual Studio, and these should be submitted as separate UserVoice requests.
aleppke
gave this 1 vote
·
As for the defects, I would like to have an option when marking as a defect to either "Create new defect" or "Mark as instance of existing defect" with a dropdown of all existing defects. The defect itself would keep track of all instances. You would then mark each instance as resolved and the defect's status as open or fixed would be based on whether there were any open instances.