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. Right now the development manager generates reviews for all a developer's check-ins each week. I would love to see a feature that would auto-generate reviews on a configurable schedule where each review is composed of all a developer's unreviewed check-ins for a given period.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. It would be great to integrate Review Assistant with the PTC Integrity source control management.

    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)
  3. When a review is approved update the Code Reviewer field on each changeset with the person who did the review.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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)
  5. Allow screenshot/pictures to be attached in a general or file comment.

    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)
  6. 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

    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. 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)
  8. The MailPassword has to be configured in clear text in settings.xml. Most companies forbid the by security policies! Add a configuration dialog instead and store the password encrypted in the xml-file.

    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)
  9. It seems that file-comparer is extracting both files from svn. Think cashing them would help. Also closing of comparer takes 1-2 seconds, and its tacking place not in separated thread so visual-studio freezes, and that’s pretty annoying.

    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)
  10. 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)
  11. 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

    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. 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)
  13. 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)
  14. We dislike that fact that comments are sent right away. Would like the ability to Save a comment before Sending a comment. There are times I like to use comments as a way to track things.
    If this could be configurable per user local settings that would be great.

    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)
  15. 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)
  16. It would be nice comments could contain rich text, or at least a couple simple styles. This could be useful for quoting code.

    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)
  17. Allow for a url like

    https://company.ontimenow.com/viewitem.aspx?id={ID}&type=incidents&force_use_number=true

    Then add a field to Reviews for Task ID: [ ]

    then show a url where {ID} is replaced with the id so the users can quick link to task management system.

    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)
  18. The autorefresh of the Code Review Board has some disadvantages while you are working on the list of files or on the list of review items:
    * Your position in the scrolling list is lost.
    * The review items are reordered according to their Open/Closed status.

    It would be better to just signal a refresh is due by coloring and or flashing the Refresh button (e.g. green or orange). The user can than choose if he wants to refresh the Code Review Board immediate or some time later.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. When I am working on my review comments one by one from top to bottom it is very disturbing that they are reordered every 10 minutes according to their Open/Closed status.

    Please make the reordering of the comments optional or just order them according to the time they are added so the ordering never changes after items are added.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 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)
  • Don't see your idea?