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.