Searching FishEye

FishEye has a powerful search engine that allows you to find changesets, committers and files. There are two methods for searching in FishEye:

Quick Search

  • Searches across all repositories connected to FishEye.
  • Suggests "quick nav" results as you type.

Advanced Search

Use Quick Search

Simply enter your search criteria in the search box in the FishEye header to search across file, repository, committer and user names, as well as commit messages and reviews ( if you are using Crucible with FishEye).

  • Use search tools and filters to refine your results. See Refining your Quick Search Criteria and Filtering Quick Search Results below.
  • Results are weighted by edit date; files edited within the last twelve months are given greater weighting.
  • There is a 100-repository limit on searches, to prevent FishEye becoming unresponsive when there are large numbers of repositories. FishEye will also limit the search to the specific repository that you are looking at, if you are already navigating within a specific repository
  • If FishEye is integrated with JIRA you can see a summary of a JIRA issue in your search results by hovering over the issue key. See JIRA Integration in FishEye.
  • See also Searching Crucible in the Crucible documentation.

Refine your Quick Search criteria

The FishEye Quick Search has a number of powerful tools that you can use to refine your search criteria before executing the search.




CamelCase pattern matching

Enter a CamelCase pattern to find matching files and directories.

BooQCTest returns results like BooleanQueryCoordTest

and BooleanQueryClassTest.

Path/File pattern matching

Enter a path/file pattern to find matching files and directories.

common/final/Actions returns results like /src/common/eu/systemworks/specialprojects/final/

Field handles

Use a field handle to restrict your search to a particular field:

  • file — file/directory names
  • commit — commit messages
  • diff — lines added/removed
  • content — file contents
  • committer — committer names

file:build.xml returns files with names matching build.xml.

Search within a directory

Use AntGlobs to search a specific directory.

Search for /src/**/gwt/*.xml and FishEye will return all files with a .xml suffix

that are below both a src and a gwt directory. e.g. src/java/com/atlassian/fecru/gwt/FecruCore.gwt.xml but not src/java/com/atlassian/fecru/ApplicationContext.xml

Search for discrete phrases

Enter a phrase in quotation marks.

Not case-sensitive.

"update version in build" returns matches for the exact string, i.e. it will not return "update build version" or" update version in file".

Filter Quick Search results

Once you have a set of search results on the Quick Search page, you can filter them to a subset of the original results. The filter controls are in the left panel of the Quick Search page in the 'Source' section.



All repositories

By default, searches across all repositories.

Choose a repo to restrict the search to just that one. For example, if you enter 'FE' then the search results page will refresh to display only files and directories in the 'FE' repository.

Files and directories

Filter your results to files and directories that have names that match the search criteria, see details below.

Commit messages

Filter your results to changeset comments that match the search criteria.


Filter your results to diffs (lines added/removed) that match the search criteria.


Filter your results to files that have content that match the search criteria, see details below.


Filter your results to committers that match the search criteria.

All projects When using Crucible with FishEye, there is a 'Reviews' section. The All projects dropdown allows you to filter reviews returned in the search results. See Searching Crucible.
Reviews Search in reviews
Comments Search for review comments
Last modified Filter by the date of the last change.
Author Filter by author name.

Use Advanced Search

The Advanced Search can only be run against a specific repository, however you can specify more precise criteria against a number of fields for that repository.

  1. Navigate to the repository that you want to search, as described in Browsing through a repository.
  2. Click the Search tab.
  3. Enter your search criteria:

Use Switch to EyeQL Search and Switch to Standard Search at the bottom of the 'Search Criteria' panel to toggle between the two search methods.

Specify criteria using the search interface

The Advanced Search interface allows you to specify search criteria for multiple fields, order the results, group the results and choose the display fields in the results. You can link to the search results, as well as save the results to a CSV file.

Please note the following:

  • Contents — Files must be non-binary, less than 5MB, and for SVN repositories, on trunk only. Only HEAD/tip revisions are searched. For older revisions, use the added/removed text search criteria.
  • File names — Antglobs can be used to specify the criteria for this field.

Specify criteria using EyeQL

Advanced Search also allows you to run searches using FishEye's powerful EyeQL query language.

Click Switch to EyeQL Search at the bottom of the 'Search Criteria' panel.

See the EyeQL reference guide for more information. If you're unfamiliar with EyeQL, consider using the Standard Search Interface to build your initial query, then switch to EyeQL to modify that.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

7 Archived comments

  1. User avatar

    Omair-Inam Abdul-Matin

    Our BAs need to search a specific set of property files in our CVS repository for property names...I've found that the content:_searchtext_ syntax returns search results in a nice visual format...

    but it searches all files.. 


    I was trying to craft a query that uses simple search to do this... e.g. file:App*Config*.properties content:search_text  but I've found that I can only search for a filetype or for content.. not both.. is there a way of specifying this search criteria... 

    If I use advanced search I can use the file name and contents fields to specify what I want.. but the search is obviously harder for non-technical ppl... and the results format is also less than ideal: no in-line preview and clicking the search results navigates the user to the revisions view which does not show the source

    if the simple search could be made to support multiple fields that would be excellent... also the advanced search could use some improvements... 

    07 Jun 2013
  2. User avatar


    Can we have advanced search on all repos?

    15 Aug 2013
  3. User avatar


    Search in content is case sensitive and search whole word only... with QuickSearch or Advanced search.

    It's almost impossible to find methods or properties name, without knowing the exact camelcase name.

    A non-case sensitive, whole word and wildcard (? * **) option whould be welcome...

    03 Mar 2014
  4. User avatar


    I find the opposite - search in content is always case-insensitive. This is a problem when you're doing something like:

    content matches "thE"

    case-insensitive search throws back over a thousand matches, a case-sensitive search would return about 3.

    Ideally there would be some way to choose whether a search was sensitive or insensitive, either by changing keyword (matches vs imatches or similar) or by modifying the search string ("(?i)thE" or similar).

    Any chance of something like that being possible?

    11 Mar 2014
  5. User avatar

    shruthi sj


    How to search more number of JIRA issues in fisheye, currently im using below one to search only one issue but how would i use it for more number of issues.


    select revisions from dir "/" where comment Matches "LIQ-48084" order by date  desc  group by changeset return path, revision, author, date, csid



    28 May 2014
    1. User avatar

      Paul Watson [Atlassian]

      Hi, have you seen the EyeQL page here: EyeQL Reference Guide?

      29 May 2014
    1. User avatar

      Dina Daftedar


      To select more than one story Id from JIRA:

      select revisions from dir "/" where comment =~ "(LIQ-48082)|(LIQ-48084)" order by date  desc  group by changeset return path, revision, author, date, csid

      14 May 2015
Powered by Confluence and Scroll Viewport