Skip to content

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/

Review Assistant

Categories

JUMP TO ANOTHER FORUM

91 results found

  1. Visual studio has built-in support for reviewing git pull requests. It would be nice to use Review Assistant instead of weak built-in tool.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. The code review board inside Visual Studio lags, stutters, and is overall not very snappy. Particularly bad is the scrolling, but also it is quite slow in expanding/collapsing comments and in opening a comparison view when double-clicking a file. Would like it to be smooth and delightfully fast.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. I would like the capability to specify at the project level the minimum number of "Accepts" allowed such that a review can be closed cleanly when that number is either met or exceeded. That way available reviewers can review without needing the entire list to accept.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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.

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. It would be nice to have a thumbs up or like type functionality to allow agreements to other comments in a review.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    60 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. I, as reviewer, can accidently set review status "Accepted"
    or I can change my decision after having a conversation with review author
    at least I can delete my comment-“defect”, so I can change decision from rejected to accepted.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Code reviews with a lot of comments become very ugly with the way comments are organized… and no way to collapse.
    having the ability to hide reviewed comments, or collapse comments and retain collapsed/hidden state across sessions for current user will help make the UI more user friendly.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Would like the ability to auto filter the changeset selection window by the currently logged in user or user entered value (that is kept from session to session.)

    The filter when adding changesets for code review is a little convoluted, the UI makes it seems like you need to enter in the full AD account name.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Some filetypes do not contain handwritten sourcecode, so they do not need to be reviewed. These file clutter the list of files to be reviewed. E.g. .csproj, .vspscc, .sln, .svcinfo, .disco, .wsdl

    Please allow an exclusion list for filetypes that do not need to be reviewed. So these files do not appear anymore in the list.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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.

    47 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Add an option for changing the font size. The comments are hard to read because of the small font size.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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

    84 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. The review overview list is very minimal. It would be nice to get more information at one glance. Now you have to open each review separatly or hover over the reviews to see things like:
    - What tasknumbers and/or changesets are involved in a review.
    - How many reviewers have accepted already

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. It is important to be able to select commits for review by searching comments field. It is hard to select commits for review based only on author name and branch name.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?