This is the documentation for FishEye 3.6. View the latest version of

Unknown macro: {spacejump}

or visit the latest FishEye documentation home page.

Skip to end of metadata
Go to start of metadata

Linking two Atlassian applications, for example FishEye and Stash, allows you to access one application's functions and resources from within the other. Linking is achieved using the Application Links plugin (sometimes called "AppLinks").

See Integrating FishEye with Atlassian applications for an overview of the benefits of integrating your other Atlassian applications with FishEye.

When linking an Atlassian Cloud instance to FishEye, your FishEye application must be accessible through port 80 (or port 443 with a valid (CA) SSL certificate).

To link two Atlassian applications:

  1. Click the 'cog' menu in the FishEye header, and choose Administration (you'll need to be logged in as an administrator to see this link).
  2. Choose Application Links in the left-hand panel. The Application Links configuration page displays links that have already been set up.
  3. Enter the URL of the application you want to link to, then click Create new link.

    Cloud to Cloud integration

    When adding the Cloud URL, use the https://instance.atlassian.net. If the https:// is not used, the link will not be completed.


    • If you check The servers have the same set of users... then this link will be configured using OAuth (with impersonation) authentication.
    • If you are not an admin on both servers you won't be able to set up a 2-way (reciprocal) application link. If you want to go ahead and create a 1-way link anyway, clear the I am an administrator on both instances checkbox.

  4. Use the wizard to finish configuring the link. If the application you are linking to does not have the Application Links plugin, you must supply additional information to set up a link with OAuth authentication.

Note that:

  • For FishEye 3.2 and later, creating a new application link now uses OAuth by default and enables both 3-legged OAuth (3LO) and 2-legged OAuth (2LO).
  • When updating older application links (that perhaps used Trusted Apps authentication) to use OAuth, 3LO is used by default, but you need to explicitly enable 2LO using the check box in the application link configuration settings.
  • Only use the 2LO with impersonation option in the application link configuration settings if your servers both have the same set of users and they fully trust each other.

When you complete the wizard, the Application Links plugin will create the link between your applications using the most secure authentication method that is supported between the two application types. After the link has been set up, it will appear on the "Configure Application Links" page. You can use this page to edit the configuration of application links to make them more secure or to change the link settings:

  • No labels