Error: Cannot add comment to this document.
Posted: Tue 03 Sep 2013 08:55
We're using Review Assistant 1.2.35 with Visual Studio 2012 Premium Update 3 and TortoiseSVN 1.8.2. The configured diff tool is "Visual Studio Internal".
Problem:
1. Dev makes change at revision 2 and creates review request.
2. Other devs make plenty of changes, working copy is updated to revision 5.
3. Reviewer starts review with updated working copy (revision 5).
4. Reviewer double-clicks on a source file src.cs to see the changes.
5. This seems to call "Compare Base and Last revision", the file is shown as "src.cs - Revision 1" on the left and "src.cs - Revision 2" on the right side
6. Now the reviewer right-clicks on a change in the right window and selects "Add Review Comment"
=> This shows the error message "Cannot add comment to this document. This file doesn't belong to any repository of the current Review Assistant project."
Why is this happening?
I believe the problem is that the working copy is at revision 5 and we're looking at revisions 1 and 2. But this is required in this case.
If at step 4 above the reviewer selects "Compare Base Revision with Working Copy", then the comment can be added just fine, but this compares revision 1 to 5, which is not what we want here.
Is this a bug or a configuration problem?
Problem:
1. Dev makes change at revision 2 and creates review request.
2. Other devs make plenty of changes, working copy is updated to revision 5.
3. Reviewer starts review with updated working copy (revision 5).
4. Reviewer double-clicks on a source file src.cs to see the changes.
5. This seems to call "Compare Base and Last revision", the file is shown as "src.cs - Revision 1" on the left and "src.cs - Revision 2" on the right side
6. Now the reviewer right-clicks on a change in the right window and selects "Add Review Comment"
=> This shows the error message "Cannot add comment to this document. This file doesn't belong to any repository of the current Review Assistant project."
Why is this happening?
I believe the problem is that the working copy is at revision 5 and we're looking at revisions 1 and 2. But this is required in this case.
If at step 4 above the reviewer selects "Compare Base Revision with Working Copy", then the comment can be added just fine, but this compares revision 1 to 5, which is not what we want here.
Is this a bug or a configuration problem?