Add an lightweight Review Board displayed as a web page at server.
As a development manager I need to track many projects and I don't want to run Visual Studio for every of them just to watch is there any update.
Or any other way of notification/summary information distributed by other means than Visual Studio.
Thanks

Pre-commit review is must to have for all type of version controls with diff/patch files or directly by uploading different version of files otherwise its going to be behind the other review tools in making of choice.

Provide the following integration points with JIRA:
- Associate code reviews with JIRA issues (e.g. review for a feature)
- Turn comments into issues (defects)

If someone submits a review that includes several revisions spanning a period of time, there's no way to determine what changes were made by the author. The only options (Compare Base and Last Revisions, etc) deal with the Base and Last Revisions. Effectively, this includes any changes made by *anyone* in-between, not just the author.

It would be good if the code review could log back to the original work item that a code review has taken place. When doing a review, it shows me the Work Items attached to the changeset (this is nice). However, when the review is done (accepted or rejected), there is no log in the Work Item that the review took place.

This has currently got to be done manually, would be great to get this full link.

Is there any way to link it or log something in the history of the work item(s)?

I'd love the ability to categorise a comment. Example categories might be coding standard, implementation, functionality. You could then report on these. E.g. Developer A received 20 comments last week, 90% of them were about coding standards. It will help to identify patterns in developers weak and strong points.

At the moment you can only "accept" or "reject", I'd like to see a third status that doesn't close the review. Thus if reviewer has questions and wants to discuss an issue via comments before deciding on accepting or rejecting they select this status.
The status could be called "Response required"

When viewing files from the "Changes" list of a code review you have to double click the file-name to have the file display with the Diff view. This then needs to be manually closed.

To improve usability, and speed up the review process, I would like to see the Diff view open in a preview tab in Visual Studio (as when you single click a file in the solution tree) and then automatically close when a new file is clicked on. As is the default behaviour of the preview tab.

Thank you.

Currently its impossible to see the branch name while doing a code review. This makes it hard for the reviewer to switch to the branch to directly make changes to it.

As a server admin I should be able to control whether my clients get upgrade notices, esp. for breaking changes where both client and server need to be upgraded together. At my company dozens of people have asked why they even get prompted for the 3.x version when the server is still on 2.x. Many companies have change control policies or software packaging regimes which prevent quick software upgrades. The ability to specify at the server that you want to suppress upgrade notices would make the job of administrator easier.

I'd like to know what exact changesets developer included in the review and want go to changeset detail page of visual studio (just like when browsing history of file and right clicking and choosing changeset details).

There are related work items but not changesets itself.

Provide more possibilities to search, filter and order the comments.
e.g. for the reviewer's name, file name, ...

Currently the Code Coverage report shows only TFS Changeset revisions and their status. It would be helpful if we can see even Shelveset revisions and their status. Teams who rely on pre-commit reviews use only Shelvesets and hence it's not of any use if they can see only Changesets in the Code Coverage report.

By default, Review Assistant launches the 'Compare Base and Last Revisions' command when you perform a comparison. Add the option to choose a default comparison action. E.g. during comparison, authors usually use 'Compare Base Revision with Working Copy' to be able to add changes to the working copy file.

As Slack is getting more and more popular, integration with ReviewAssistant would be really useful.

All email notifications could be sent to Slack too.

Add integration with avatar service - gravatar. It will make easy user identification for Code Review participants. This is implemented in Crucible product for example.