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

    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. We started using Review Assistant before it had AD integration, so we have a bunch of users with logins/passwords. If we want to change one of those users to use AD, we need to remove their account, add a new one, and then manually add them back to every project they had access to. It would be nice if there were an easy way to switch an existing user to use AD credentials.

    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. 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)
  4. 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)
  5. Currently users are added individually. Allow the addition of Active Directory groups as members to allow the AD group members access to code review. This makes management of access easier so that users do not need to be added individually but are added automatically when added to the AD group.

    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)
  6. 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)
  7. 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)
  8. 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)
  9. 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)
  10. 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)
  11. 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)
  12. 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)
  13. 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)
  14. 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)
  15. 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)
  16. 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)
  17. 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)
  18. 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)
  19. 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)
  20. 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)
  • Don't see your idea?