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. The 'a review changed pop-up' appears on any change in a review. This can be very distracting. It would be nice to be able to configure when and or it appears:
    - or you want to see it at all
    - when you want to see it
    - or it stays visible or disappears after a while

    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)
  2. Implement reminder feature, so I can be notified about pending review to complete.

    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)
  3. The UI of the Code Review Board is getting cluttered. Many different kinds of elements yield a suboptimal experience: I see little icons, big buttons, blue links, tiny expander triangles, and text instructions in arbitrary places. Also, the UI is not optimized for the most common use cases/value streams:

    1) Create a review, add revisions, add reviewers, done.
    2) Open a review, examine each file and make comments, done.
    3) Open a review, read comments, open files to consider making changes, reply to comments, add new revisions, done.

    Recommend a GUI expert to tweak the UI.

    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)
  4. Shelvesets that are created automatically during the code review process are left hanging around. This adds clutter to TFS. Add an option to automatically delete shelvesets from closed reviews added by review assistant older than x number of days.

    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)
  5. 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)
  6. Create checklist (predefined depending on the project particularities) with programming rules/notes that must be verified for each code review. Example: If a certain config is modified do not forget to announce sysadmin, etc.

    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

    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)
  7. When adding revisions to a review created from a shelveset, RA will query shelvesets from TFS. However, our company has thousands of developers, and the number of shelvesets is very large. In the default query conditions of Add Revisions, "Author" and "Get last" are empty, resulting in VS having no response for a long time when clicking Add Revisions. We hope that when adding revisions with shelveset, RA will specify Author as the current user by default, thus speeding up the query.

    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)
  8. Option to archive a project. Or hide from projects overview

    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)
  9. We use VS Code more than Visual Studio when developing web based applications. It makes sense to support all Visual Studio products.

    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)
  10. Allow Review Assistant to be run behind a load balancer so that the server can be patched and upgraded without downtime.

    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)
  11. When you click the View link, directly open the review that caused the pop-up to appear. Now you end up in the review overview list without knowing which review was changed.

    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)
  12. Whenever I am trying to initiate an ad-hoc review by selecting code in .cs file, I am getting error: "File association with Review Assistant project failed. Check the repository settings." I am using Visual Studio 2015 Enterprise and latest version of ReviewAssistant.

    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

    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. I would like to be able to execute certain actions once a review has been completed and accepted by all reviewers

    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)
  14. Currently, each user that installs RA needs to manually set their Working Directory. If, for some reason, they decide to move their TFS Workspace (or switch workspaces, because you can have many), then the user must also modify the Working Directory field in RA. The Active Workspace information is available in the TFS API, so when the VCS for a repository is set to TFS, then RA should always set the Working Directory to the active Workspace.

    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

    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)
  15. If you add a revision that has a lot of items to it, you can only see several items at a time.. then you have t scroll for a long time and it can be hard to get scroll (because the scroll area is too small with too many items).

    It would be better if we could resize this box to give it a larger height so we can view more items.

    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)
  16. 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)
  17. Make the following configurable:
    The ability to move code from the new version to the old version using Code Compare. Currently this is allowed and from what we have seen not configurable.

    I would prefer code reviews to be read-only by default.

    The intent of the code review is not to change code but to review code.

    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

    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)
  18. Currently my team and I tie all reviews for a given product version together by starting the review title with the version number (i.e. 1.4.0 - Enhancing Clients Screen). This lets us find all reviews associated with version 1.4.0 by typing "1.4.0" in the Filter box on the Code Review Board, but it's very limited. If 4 items come back, and we select one, we can see the review, but none of the comments, as the comments don't contain the text "1.4.0". So to review the comments, we have to clear the filter. Now if we click the back arrow,…

    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

    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)
  19. Send email from review creator user. So instead of me configuring the server with reviews@mycompany.com, I could configure it to come from the user name + the domain who is making the changes. So if I use windows auth, and my username is mycompany\myname, chop the "mycompany\" part and send the email from mynamed@mycompany.com.

    That way I can also easily carry on an email conversation when change emails are sent

    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)
  20. 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)
  • Don't see your idea?