Linking FishEye to JIRA

JIRA Software is Atlassian's issue-tracking and project-management application. You can connect FishEye to JIRA Software for one or both of the following:

Configuring those two aspects are separate processes, and are described on this page. Note that you can link FishEye with one or more instances of JIRA Software. If you're linking FishEye to an Atlassian Cloud JIRA instance, please see Link to server applications from Cloud.

On this page:

Your user tiers don't need to match between JIRA Software and FishEye/Crucible in order to integrate them. JIRA Software users that are not FishEye users will see the same view as FishEye users within JIRA Software, but will not be able to log in to FishEye to view the source/reviews.

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 your 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.

Integrate with JIRA Software

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

See Linking to another application for details about linking FishEye and JIRA servers to get those integration benefits.

See also Enabling Smart Commits.

Use JIRA Software to manage FishEye users

See Connecting to JIRA for user management.

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 manual refresh of the FishEye 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: go to Administration > FishEye Configuration and click Refresh Cache (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 recognize custom JIRA issue key formats – FishEye assumes that JIRA issue keys are of the default format for JIRA 5.0 and later: that is, between 2 and 10 characters long and contain only uppercase letters followed by a hyphen and the issue number, for example, FECRU-123.  The regex describing this pattern: [A-Z]{2,10}-[0-9]+
  • 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 Software. 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">

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport