Review Assistant

Review Assistant is a code review plugin for Visual Studio. Peer code review tool helps you to create review requests and respond to them without leaving Visual Studio, improve code quality and ship software with less defects, automate the process with minimum overhead.
http://www.devart.com/review-assistant/

How can we improve Review Assistant?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Review Board in the browser

    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

    83 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. JIRA Integration

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

    58 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Comparison highlighting only changes made by revisions

    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.

    51 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support pre-commit review for all VCS

    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.

    44 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Ability to categorise comments

    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.

    35 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. API for all basic interactions

    There are over 60 requests for some API level access to the product. There are a ton of standard and custom issue tracking systems out there that could tie into your product. In our case we would love to tie TFS check in events to create and update reviews automatically. This seems like a major missing feature compared to a lot of other products in the space. Yours would work best if the API was exposed. People have been asking for over 2 years.

    The command line is clunky and insuffiecient, or at least not documented well enough to be…

    33 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add link back to Work Item in TFS after code review complete/rejected

    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)?

    32 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Renamed/moved files support

    Currently, when a file is renamed and/or moved, 2 entries will appear in the changed files list. The old file will appear as deleted and the new file will appear as added. While by itself is only a nuisance, if any changes occur in the added file there is no way to compare them with the deleted file. Since rename/moving a file may also introduce changes in the file itself (like for example a changed namespace and class name) it becomes problematic to code review these cases.
    As far as Git is concerned (with the proper git command) there exists…

    19 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  9. Ability to search, filter and order comments

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

    19 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Option to set a default action when opening comparison

    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.

    19 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. Control client upgrade notices from the server configuration

    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.

    15 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  12. Accept and Reject Files as a Whole

    I really need the ability to accept or reject files as a whole.

    Consider reviews with lots of files, or reviews with complex or very interrelated code spread among multiple files. The reviewer is likely to jump back and forth between multiple files to ensure the solution that is being reviews is solid. Once a reviewer has determined that the file is acceptable, they need to be able to mark it as such so that as they continue on they can keep track of that. Otherwise, if they get interrupted during the review (again consider large reviews that likely will…

    13 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Slack Support

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

    All email notifications could be sent to Slack too.

    13 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. TFS Shelvesets in Code Coverage report

    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.

    11 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow custom reports at the user or global level

    It’s becoming really painful to run most of my reports because of the lack of ability to save custom values like filters, project/report type combos and date ranges so I can run them again later. It would be nice if I could save these as a "custom" report entry on the list so I could reuse my filters since the GUI for filters is very combersome for more than one or two custom values. If there could be user-specific or global saved report definitions that would be great, because I would like to allow multiple project owners to be able…

    8 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add Due Date to the code reviews

    To have Due Date associated with code review and let code reviewers know that due date is coming up via email will be great functionality to have.

    Basically - coder should be able to add a date for code review deadline and reviewer should get ample notification if code review is not completed within that due date.

    8 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Gravatar integration

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

    8 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Adding reviewers by groups

    Definitly needs groups when you don't know or want to assign the review to a specific person.

    8 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Smiles in CodeReview board

    Hello! Could you please implement the smiles in Code Review board? It will be great!

    7 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add Thumbs Up or Like to a comment

    It would be nice to have a thumbs up or like type functionality to allow agreements to other comments in a review.

    7 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5
  • Don't see your idea?

Review Assistant

Feedback and Knowledge Base