89 results found
-
Add an option to delete shelvesets after a review is closed
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 -
PTC Integrity SCM integration
It would be great to integrate Review Assistant with the PTC Integrity source control management.
1 vote -
Allow use of Active Directory groups to manage membership
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 -
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 -
Automatically generate reviews on a managable schedule
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 -
Attach screenshot
Allow screenshot/pictures to be attached in a general or file comment.
1 vote -
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.
10 votes -
For TFS VC, link user's TFS Workspace to RA's Working Directory
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 -
TFS: Update Code Reviewer field
When a review is approved update the Code Reviewer field on each changeset with the person who did the review.
4 votes -
MailPassword encrypted
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 -
Resize Code Review sections in Code Review Board Tab
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 -
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 -
Speedup opening and closing of files in file comparer.
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 -
Ability for all reviewers to change their decision (Accepted/Rejected) any time they want, without need to wait for review to be updated or
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 -
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 -
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 -
Create custom checklist with programming rules that must be verified for each code review
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 -
Ability to hide or collapse comments in review panel
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 -
Changeset Selection Window Improvements
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 -
Would like the ability to split the Saving and Sending of a comment into two actions.
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
- Don't see your idea?