rwilkinson
New Contributor
Joined 8 years ago
User Profile
User Widgets
Contributions
Visual Studio Extension - Create Code Review From Changeset
The current workflow for creating code reviews within Visual Studio isn't as seamless as it should be. Developers already have efficient means to view an existing changeset or commit. Collaborator should extend these views so that the code review "Changeset" or "Commit" search UI is no longer necessary. Current workflow: Developers check-in, shelve, or commit code changes. Users goes to Collaborator toolbar and selects "Add Materials". User can then select that they want to begin by selecting a changeset. User locates their changeset via certain filtering options (this can take awhile). User proceeds to finish filling out the code review information. Proposal 1: Developers check-in, shelve, or commit code changes. Immediately after check-in user can view Changeset Details. User given option to initiate a Collaborator Code review which passes on the specific changeset so the wizard advances automatically. User proceeds to finish filling out the code review information. Proposal 2: Developers check-in, shelve, or commit code changes. Users when viewing "History" can see recent changesets. User right-clicks a specific changeset and can choose to create a Collaborator Code review passing on the specific changeset so the wizard advances automatically. Extra credit: Upon right-click call collaborator API and show user if a code review already exists for this changeset or commit.2.1KViews0likes0CommentsAllow Observers to more quickly claim Reviewer role via review pool action
Scenario: A user has set up an observer role subscription for certain files or authors. This user is also a member of a review pool group. A review comes in where the observer subscription has taken effect and that user wishes to claim the review as reviewer. The user is unable to click the Action icon to automatically become a Reviewer. User has to Edit Users -> Modify their role -> Done Editing. Proposal: Rather than require the reviewer to Edit Participants and change their role we feel that this review pool action should automatically convert a user's observer role to reviewer without it requiring a manual edit.5.8KViews0likes3CommentsCode Review Comment - Multi Line Selection
User experience would be greatly improved if the reviewer could associate their comment or defect to a range of lines instead of just a single line. Additionally, if that range could also be inclusive of characters within a single line that would also be appreciated. When comments or defects are part of a large block of code being able to accurately call out an area of code instead of just a top line of code is helpful.7.1KViews20likes3CommentsDiff tool option - Do not display line #s inline
Would like to see a display option added in the web view of the diff tool screen where Line #s would not be shown. We have a few use cases where a .sql script is being reviewed by a reviewer and they want to copy/paste the script into their IDE to run. When you attempt to copy multiple lines you end up copying the line #s as well which requires you to scrub the resulting paste before you can execute your sql. Alternatively, allowing the line #s to be outside of the selecting content area would also resolve this issue.2.5KViews2likes0CommentsRe: Plugin support for Visual Studio 2017
VS plugin is nearly unusable. My team had meeting with smartbear folks and was told they are actively addressing numerous vs plugin improvements. For those of you who are using the plugin in its current form I'm surprised you're able to use it at all. My team had to rely on the desktop app for creating and adding files to reviews and then the web client to perform the actual review workflows. I hope the future is bright for us Visual Studio teams. Rudy3.9KViews0likes0Comments