91 results found
-
Allow enter key to switch from diff view to working copy view
The GitHub Visual Studio extension v2.4.3.1737 just did this and it's pure genius. See https://haacked.com/archive/2018/03/15/github-vs-pr-features/ for details. This would probably be easier to add this feature than setting up the UI and persistence to implement the idea at https://devart.uservoice.com/forums/145340-review-assistant/suggestions/5744139-option-to-set-a-default-action-when-opening-compar and nets the same result.
4 votes -
Add a possiblity to specify computer name in email links.
Computer name visible on network can differ from the name detected by RA server. So links in notifications cannot be opened. it would be great if there will be a possibility to override this name in RA server config.
1 vote -
Allow emails to be sorted into conversations by keeping the subject line consistent
Or through some other mechanism like a conversation ID. Our old tool (Swarm) used the exact same subject line for every email, which I think Outlook and other email apps are able to use to sort all messages about a review into the various conversation views you see around these days. Review Assistant seems to constantly alter the subject line so my Review Assistant email folder is just a jumbled mess of seemingly unrelated emails. If you could add an option to not prevent this sorting from occurring (in Outlook, at least?) I think it would greatly assist most people's…
5 votes -
Display filename(s) and/or at least the revision/changeset number(s) in email notifications
I want to be able to search my email history for a file name and find which review had been created for it (with the link). Being able to search by the revision/changeset number would also be helpful.
If the New Review notification (as well as the notification that a new revision/changeset has been added to a review) would list the revisions and the files within each, that would be very helpful.
1 vote -
Show the review number in the Code Review Board
The only place I see the review number is in the notification emails. I want to be able to reference a review in conversation by number, as the titles can be verbose and difficult to distinguish from each other in some cases. Either show it all the time just before the title, or at least display it in the hover text.
1 vote -
Change "Reject Changes" to "Recommend rework"
"Accept changes" is a good disposition, but it strikes me as suboptimal to have the alternative be "reject changes". It seems like that implies that the changes should be rolled back or totally undone. More often, we want to say that "I am done with the review and I think something needs to be changed."
So perhaps there is a better way to word it, but the best I can think of is that the ways to Complete Review should be "Accept changes" and "Recommend rework". Perhaps "Reject changes" could be a third option, but I wouldn't use it very…
5 votes -
Control client upgrade notices from the server configuration
As a server admin I should be able to control whether my clients get upgrade notices, esp. for breaking changes where both client and server need to be upgraded together. At my company dozens of people have asked why they even get prompted for the 3.x version when the server is still on 2.x. Many companies have change control policies or software packaging regimes which prevent quick software upgrades. The ability to specify at the server that you want to suppress upgrade notices would make the job of administrator easier.
15 votes -
Allow review creator to annotate the contents of a review.
Often, I would like to add explanation to changes I'm including in a review. I can this in an overview comment, but in a review with lots of files, it's nice to give preparatory remarks on individual files, or specific lines of code in a file.
1 vote -
Code Review Board UI tweaks for better usability
The UI of the Code Review Board is getting cluttered. Many different kinds of elements yield a suboptimal experience: I see little icons, big buttons, blue links, tiny expander triangles, and text instructions in arbitrary places. Also, the UI is not optimized for the most common use cases/value streams:
1) Create a review, add revisions, add reviewers, done.
2) Open a review, examine each file and make comments, done.
3) Open a review, read comments, open files to consider making changes, reply to comments, add new revisions, done.Recommend a GUI expert to tweak the UI.
3 votes -
Accept and Reject Files as a Whole
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 -
Allow custom reports at the user or global level
It’s becoming really painful to run most of my reports because of the lack of ability to save custom values like filters, project/report type combos and date ranges so I can run them again later. It would be nice if I could save these as a "custom" report entry on the list so I could reuse my filters since the GUI for filters is very combersome for more than one or two custom values. If there could be user-specific or global saved report definitions that would be great, because I would like to allow multiple project owners to be able…
8 votes -
Post Review hooks
I would like to be able to execute certain actions once a review has been completed and accepted by all reviewers
2 votes -
Add Header to Mails so they can be filtered more intelligently
It would be nice if Review Assistent would add a message header to the mails it sends out that has the project name so they can be filtered easier in mail clients like Outlook like:
X-ReviewAssistant-Project: FooBar Project
While it is in the title of the message, it would be better to have it as a header to be able to filter on.
1 vote -
Ability to "deploy" review assistant updates from the server
It takes a lot of work to coordinate updates to the server side and dozens of clients. Since the install is the same executable, it should be reasonable to make an option in the client settings to update to latest version. All users using an old version would get a notification which would take them to the RA settings pane. There would be a button/link to "update now" this would kick off a download from the RA server which would deliver the exe to the user and execute it. (I silent install would be phenomenal!)
1 vote -
Mandatory Reviewers for certain SVN URL(s)
We would like to setup Review Assistant such that if a review occurs on certains files / url(s) that there are mandatory reviewers automatically added to the review
1 vote -
Add ability to select or unselect a range of files for review.
When creating a review, after choosing the changesets to include in the review, I often need to unselect a large number of files from the review, because they are generated files that don't need to be reviewed. Currently, the only way to do this is to click the checkbox next to the file for each file. I would like to be able to shift-select a large range of files and then unselect all with a single click.
1 vote -
Add all changesets linked to a tfs task
TFS allows developers to link work items by ID to a check-in. This is often enforced by a rule to make sure devs always do this.
Now the reviewer has to manually pick the changesets linked to the TFS item one by one from the TFS history.
It would be great if these TFS items could be used as the source for the changesets to import to perform the review on.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 -
Ability to convert a user with login/password to AD account
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 -
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
- Don't see your idea?