44 results found
-
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
-
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.
-
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 -
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 -
Add an "observer" role
The observer would be able to view and participate in the review, but wouldn't be required to complete it. I.e., they could add comments and even bugs, but if they do not participate in the review at all (e.g., due to time constaints) the reviewer(s) could still end the review as normal with the observer required to interact at all. This would give everyone notification that the review has begun, and make it clear that their role was optional, so to speak.
21 votes -
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 -
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 -
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
-
Third status for review - "Response Required"
At the moment you can only "accept" or "reject", I'd like to see a third status that doesn't close the review. Thus if reviewer has questions and wants to discuss an issue via comments before deciding on accepting or rejecting they select this status.
The status could be called "Response required"19 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 -
Preview the Diff page when single clicking on a file in the changes list.
When viewing files from the "Changes" list of a code review you have to double click the file-name to have the file display with the Diff view. This then needs to be manually closed.
To improve usability, and speed up the review process, I would like to see the Diff view open in a preview tab in Visual Studio (as when you single click a file in the solution tree) and then automatically close when a new file is clicked on. As is the default behaviour of the preview tab.
Thank you.
18 votes -
Ability to customize the reports
Mainly to insert or delete columns in the reports.
1 vote -
28 votes
-
Ability to submit a code change for Review mandatorily
I would like to have the members of my project compulsorily submit a review for every line of code change they make, to minimize the defects in a code change. In short, Mandatory Pre-Commit! It should not allow the Author to check-in to TFS without a review!
1 voteWe’ve already implemented this feature. See http://blog.devart.com/creating-tfs-custom-check-in-policy-part-1.html for more information.
-
13 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 -
Silent fail when server isn't accessible
I work in a disconnected fashion quite a bit which means the server won't be available. Today when I open VS I get a modal dialog informing me that it could not connect. I would like to have an option to suppress that either by not auto-reconnecting (preferred as it allows me to connect when I care about) or silently failing.
1 voteReview Assistant warns about broken connection only if you perform a manual connection/refresh. In other situations, it silently swallows the error, and shows the message on the status bar.
If you exprience another behaviour, please write to our support: http://www.devart.com/company/contactform.html?product=review-assistant
-
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. -
Ability to export / get a report on a code review
Although version 2 has added reports and metrics, there is still no option to get a report on a single code review (eg see all comments grouped by filename)
26 votes
- Don't see your idea?