Trying to anchor a patch for a file with no indexed revisions fails

Summary

FishEye lists a file even if its last change occurred prior to the Start Revision set for the repository, but it fails anchoring a patch to it with the following message:

 
No repository found to anchor patch to 
Crucible tried to anchor your patch to 'patch3', but did not find any matching revisions. You will not be able to do iterative reviews on this patch. 

Nothing is shown in the logs and, as the file actually appears as listed, it is not clear why the patch is not anchored.

Test Scenario

• File changed: readme
• Latest revision for the file in the repository: 33
• Start revision in Crucible: 36
• Repository's current revision: 96

Steps to Reproduce

1. Apply any change to the file readme in the repository.
2. Create a patch:

    
   svn diff > patch.txt 
   

3. Try attaching the patch. The "No repository found" message will show up.

Notes

The Git and Mercurial related use case is described in the CRUC-7523 ticket.

Workaround

1. When generating the patch, specify the current revision:

    
   svn diff -r96 > patch.txt 
   

2. Try attaching the patch. It will be succesfully attached, containing the changes not commited yet against the latest revision of the repository.