Due to a change on the indexing engine of FishEye the quick search will not consider has a valid path the query string that contains the physical repository structure (trunk, tags,branches).
For example:
The user could write on a JIRA issue description or a Confluence page the following relative path expression:

source:trunk/src/Foo.java

That would create a link like this:

http://<Studio_server>/source/qsearch/TST?q=trunk%2Fsrc%2FFoo.java

And it would do a quick search on FishEye looking for a source file under the path 'trunk/src/Foo.java'

The new improved search on FishEye requires that the search doesn't contains the repository structure as part of the query string, so the same expression needs to be rewritten as:

source:src/Foo.java

That will create a link like this:

http://<Studio_server>/source/qsearch/TST?q=src%2FFoo.java

That will find all the occurrences of 'src/Foo.java' on the FishEye repository.

Due to the complexity of repositories structures supported by FishEye it's very unlikely that we could come up with a smart solution to address this issue, instead the user will need to fix any similar expression, removing the trunk, tags, branches part of the relative source path.

This problem doesn't affect the absolute path expressions. They will continue to be linked directly to the specific file on the FishEye repository.