44 results found
-
Select project in the Code review board
It would be nice to include the combo box to select projects directly in the "Code review board" panel instead of in the Visual Studio menu bar.
9 votes -
Comments and answers in code window
Make comments and answers appear in ballons in code window like in your product description images
http://www.devart.com/review-assistant/images/code-discussion.png9 votesIn version 2.1 we’ve re-designed code editor markers and popup windows for comments. Now you can view a comment and change it’s status without switching to Code Review Board window.
-
Do not count Administrator as licensed user
By buying 5, 10 or 25 users licence I would expect that we can add same number of active directory users.
8 votes -
TFS: Show links to work items associated with check ins
When setting up a review, it would be great it Review Assistant can include hyperlinks to the Work Items (Bugs/Tasks) associated with the TFS changesets. These work items typically provide the context for the work done and it would be great to have easy access to read them from within the Code Review Board
7 votesWe have just released Review Assistant 2.0.
What’s new:
http://www.devart.com/news/2013/reviewassistant20.html -
Reviewing shelvesets in TFS
Support reviewing of shelvesets in TFS would be an awesome feature, allowing us to have all the pros from uncommitted and commited features and none of the cons.
7 votes -
Automatically create shelveset for pre-commit reviews
As described in more detail here:
http://forums.devart.com/viewtopic.php?f=49&t=29267
The manual process in creating shelvesets prior to pre-commit reviews is cumbersome and potentially error prone. The in-built Visual Studio workflow manages this problem by automatically creating a shelveset from the pending changes upon creation of a pre-commit review.
It would be great if Review Assistant could provide this as an option as it would really smooth out the pre-commit review process.
6 votesWe’ve implemented this feature in version 2.5.
It’s called ‘Pre-Commit Code Review Policy for TFS’
http://www.devart.com/news/2014/reviewassistant25.htmlPlease check it out.
-
GIT support
Plain and simple, a lot of individuals and companies (including where I work) have come to the conclusion that GIT suits their needs better than Mercurial (HG) on Windows. I don't think anyone would revert this decision just to be able to use Review Assistant.
This is a shame since Review Assistant looks absolutly awsome in other respects (Visual Studio integration). GIT support would make it an instant sale, at least where I work.
6 votes -
No mail notification for single comments
If e-mail notifications are enabled, an email is sent to the code author for every code comment that a reviewer creates. This can quickly generate 30-40 emails that are sent out to the author for one reviewer, not to mention when multiple developers review code. The code author will get an email if the review was accepted or rejected by the reviewer anyway, so an email for every single code comment is not needed. So the events that generate an email should be configurable, so email for single comments can be disabled, e.g., by introducing a log level.
4 votes -
User management from TFS cannot be used
When using TFS all users must be entered for Review Assistant again. Instead users and groups already configured in TFS should be used.
3 votes -
Remove any file and any revision from review
Let author to remove any revision added to review without finding exect commit in version control system.
Also let author to delete from review any file by context menu on item in file list3 votes -
Report of changesets that do not have reviews
We require that our developers submit a review for all of their check-ins. They can check-in code, and don't even have to submit a review immediately following the check-in, but have to eventually. Presently, there is no way of monitoring if the developers are doing this.
This would be solved with a report that showed all of the Changesets that do not have reviews associated with them for a given time-frame. That way we could see if a developer submitted a Changeset but never submitted a Review.
Also, developers could use such a report to check to make sure that…
3 votes -
Allow us to enter which windows credentials to use
You allow windows credentials to be used to login, but you don't allow us to specify our own windows credentials.
For example, I regularly work from home on a VPN from a non-domain joined machine. I would like to be able to able to type my domain credentials in so that I can authenticate as my Active Directory user.
I have tried using Windows Credential Manager to get around this problem, but have not had any joy.
3 votesYou already can achieve this by using the “Review Assistant Authentication” mode and enter your Active Directory credentials there. In some cases you should enter Active Directory credentials in full notation. eg. user@domain.local
We will make it more explicit by adding the information to the help. -
Allow ability to add an email group only for notifications
It would be cool to allow a way to add an email group either at the project level or at review time that get all email notifications but don't need to participate. In this way a team could watch a review and if say they were QA, they'd know when the review is done and ready to test.
2 votes -
TFS: create a review by specifying Work Items and automatically add related revisions
Its great that reviews show you related work items once you select change sets to review, but it would be very useful to be able to start by picking a work item that has a bunch of change sets related to it, and have it pull in those revisions automatically.
This is useful in the scenario that you have several developers working on one PBI and you want to do a single code review of all their changes at the end. All you need to do is put in the PBI number and get all their revisions, currently you have…
2 votesThis functionality is already implemented. See http://www.devart.com/review-assistant/docs/reviewing_work_item_code.html
-
Mail notifications: Add feature to disable certificate validation
When configuring mail notifications, it's possible to use SMTP with SSL.
Unfortunately when using self signed certificates, this will result in an error and no mail will be sent.=> Please add another option to settings.xml to disable certificate Validation.
2 votes -
Inclusion of revisions/files from several repositories to one review
We use several repositories and we want to be able to create reviews including revisions/files from several repositories to one review. For now we can choose only one repo to include it to review, switching to another repo resets the list of revisions/files selected for prev. repo.
2 votesWe have just released Review Assistant 2.0.
What’s new:
http://www.devart.com/news/2013/reviewassistant20.html -
Feedback forum
Please add a support forum for Review Assistant. There are currently bugs in the product that I would like to highlight and I don't think the UserVoice site is the right place to do it.
2 votes -
A hell of a great product!
Thank you for sharing this product with the community, It does what it's meant to, excellently. Code Compare, Code Review
2 votes -
Display Comment and reply date
It would be useful to see the date of the creation of a comment or a reply. Maybe as a tooltip, then it would not clutter the interface
1 vote -
encrypted DB connection
In settings.xml the DB connection uses http which is unencrypted. Tool like SonarQube also provide encrypted DB connections. Many companies forbid unsecure DB connections. You should use a https connection instead.
1 voteReview Assistant already has the feature for encrypted connection to the server http://www.devart.com/review-assistant/docs/index.html?configuring_https_connection.html
- Don't see your idea?