Initial configuration in JIRA

You should check that the instances of JIRA that you wish to link to FishEye are configured to accept remote API calls; in each JIRA instance, go to Administration > System > General Configuration and turn on Accept remote API calls (under 'Options'). A restart is not required. See JIRA options for more details.

Quick setup with the FishEye Setup Wizard

When you are installing FishEye, the setup wizard allows you to configure the JIRA connection automatically. This is a quick way of setting up integration with JIRA for user management. See Configuring JIRA integration in the Setup Wizard.

If you did not set up JIRA integration during FishEye setup at install time, you can still configure that from the FishEye administration area as described below.

Integrating with JIRA

See JIRA Integration in FishEye for an overview of the benefits you get when FishEye and JIRA are integrated.

Integrating FishEye with JIRA relies on configuring an application link between the FishEye and JIRA servers. See Linking to another application for guidance on doing that.

See also Enabling Smart Commits.

Connecting to JIRA for user management

Project links

We do not recommend the use of project links with FishEye 2.9 and later, if you have JIRA 5.0 or later as well as the latest version of the JIRA FishEye Plugin. This is because application links now provide all of the functionality previously available with project links. However, project links are retained for the following reasons:

• Setting up project links provides a way to restrict the scope of JIRA searches to a specific FishEye repository. 
• Legacy configurations can continue to use project links without any need for changes.
• Third-party plugins may continue to rely on project links for their functionality.

Notes

• JIRA requires FishEye to manually refresh repository cache when repository changes are made — When a repository is removed, or when there has been any change in FishEye repositories, JIRA does not update the FishEye repository list cache automatically. You must manually refresh the repository list cache. This is done in JIRA: 'Administration' > 'FishEye Configuration' > 'Refresh Cache' link (next to 'Repository List Cache')
• FishEye doesn't check for invalid JIRA issue keys – FishEye doesn't check for invalid issue keys, such as 'UTF-8'. An error will result if FishEye tries to connect to an issue that doesn't exist.
• FishEye doesn't recognise custom JIRA issue key formats – FishEye assumes that JIRA issue keys are of the default format for JIRA 5.0 and later: that is, up to 10 letters, followed by a hyphen and the issue number (i.e. [a-zA-Z]{10}-[0-9]+), for example FishEye-123. 
• If FishEye/Crucible will be running on the same machine as JIRA (already installed), you need to ensure that the URL paths are different for FishEye/Crucible and JIRA. Change the default FishEye/Crucible path as follows:
  

  • Edit the config.xml in your FishEye/Crucible data directory.
    Add the context attribute to the web-server  element:

    <web-server context="/fisheye">