91 results found
-
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 -
Interaction with Code Compare tool Read Only
Make the following configurable:
The ability to move code from the new version to the old version using Code Compare. Currently this is allowed and from what we have seen not configurable.I would prefer code reviews to be read-only by default.
The intent of the code review is not to change code but to review code.
2 votes -
Grouping Reviews for easy search / retrieval
Currently my team and I tie all reviews for a given product version together by starting the review title with the version number (i.e. 1.4.0 - Enhancing Clients Screen). This lets us find all reviews associated with version 1.4.0 by typing "1.4.0" in the Filter box on the Code Review Board, but it's very limited. If 4 items come back, and we select one, we can see the review, but none of the comments, as the comments don't contain the text "1.4.0". So to review the comments, we have to clear the filter. Now if we click the back arrow,…
2 votes -
JIRA Integration
Provide the following integration points with JIRA:
- Associate code reviews with JIRA issues (e.g. review for a feature)
- Turn comments into issues (defects)60 votes -
Send email from username triggering the email
Send email from review creator user. So instead of me configuring the server with reviews@mycompany.com, I could configure it to come from the user name + the domain who is making the changes. So if I use windows auth, and my username is mycompany\myname, chop the "mycompany\" part and send the email from mynamed@mycompany.com.
That way I can also easily carry on an email conversation when change emails are sent
2 votes -
Option for changing the font size
Add an option for changing the font size. The comments are hard to read because of the small font size.
2 votes -
Gravatar integration
Add integration with avatar service - gravatar. It will make easy user identification for Code Review participants. This is implemented in Crucible product for example.
8 votes -
Rich text comments
It would be nice comments could contain rich text, or at least a couple simple styles. This could be useful for quoting code.
1 vote -
Option to set a default action when opening comparison
By default, Review Assistant launches the 'Compare Base and Last Revisions' command when you perform a comparison. Add the option to choose a default comparison action. E.g. during comparison, authors usually use 'Compare Base Revision with Working Copy' to be able to add changes to the working copy file.
19 votes -
Add project task url in settings
Allow for a url like
https://company.ontimenow.com/viewitem.aspx?id={ID}&type=incidents&force_use_number=true
Then add a field to Reviews for Task ID: [ ]
then show a url where {ID} is replaced with the id so the users can quick link to task management system.
1 vote -
Add link back to Work Item in TFS after code review complete/rejected
It would be good if the code review could log back to the original work item that a code review has taken place. When doing a review, it shows me the Work Items attached to the changeset (this is nice). However, when the review is done (accepted or rejected), there is no log in the Work Item that the review took place.
This has currently got to be done manually, would be great to get this full link.
Is there any way to link it or log something in the history of the work item(s)?
32 votes -
Ability to categorise comments
I'd love the ability to categorise a comment. Example categories might be coding standard, implementation, functionality. You could then report on these. E.g. Developer A received 20 comments last week, 90% of them were about coding standards. It will help to identify patterns in developers weak and strong points.
35 votes -
Add exclusion list for filetypes that do not need to be reviewed
Some filetypes do not contain handwritten sourcecode, so they do not need to be reviewed. These file clutter the list of files to be reviewed. E.g. .csproj, .vspscc, .sln, .svcinfo, .disco, .wsdl
Please allow an exclusion list for filetypes that do not need to be reviewed. So these files do not appear anymore in the list.
7 votes -
Do not autorefresh the Code Review Board. Just signal a Refresh is due.
The autorefresh of the Code Review Board has some disadvantages while you are working on the list of files or on the list of review items:
* Your position in the scrolling list is lost.
* The review items are reordered according to their Open/Closed status.It would be better to just signal a refresh is due by coloring and or flashing the Refresh button (e.g. green or orange). The user can than choose if he wants to refresh the Code Review Board immediate or some time later.
4 votes -
Do not reorder the comments in the Code Review Board
When I am working on my review comments one by one from top to bottom it is very disturbing that they are reordered every 10 minutes according to their Open/Closed status.
Please make the reordering of the comments optional or just order them according to the time they are added so the ordering never changes after items are added.
4 votes -
Maintain the scrolling position in the list of changes on autorefresh
When I am working on the list of changed files to review them one by one the list is positioned back to the top every 10 minutes when the Code Review Board refreshes automatically.
Every time I have to reposition the list to my last scrolling position to be able to continue reviewing the files.
1 vote -
2 votes
-
2 votes
-
Support pre-commit review for all VCS
Pre-commit review is must to have for all type of version controls with diff/patch files or directly by uploading different version of files otherwise its going to be behind the other review tools in making of choice.
47 votes
- Don't see your idea?