Downloads (PDF, HTML & XML formats)
[FishEye Knowledge Base]
This page describes how to upgrade an existing application link. You may want to upgrade an application link in either of the two situations below:
On this page:
When you upgrade from a FishEye version that does not include Application Links to a version that does, you will have the option of converting any Trusted Applications or OAuth links to Application Links. The advantage of converting your links to Application Links is that link configuration will be simplified in future.
To upgrade an application link when FishEye has been upgraded to include Application Links:
![]() |
![]() |
![]() |
![]() |
Step 1
|
Step 2
|
Step 3
|
Step 4
|
Screenshots above: Upgrading an application link for your local application
When an application link is created between a version of FishEye that supports Application Links, and a remote application that does not (either a non-Atlassian product, or an older version of an Atlassian product that did not ship with Application Links), this link is configured to run in 'legacy mode'. While there is no distinguishable difference to a user, connection and configuration without Application Links is a little different. For example:
If you upgrade your remote application to a version that does support Application Links, the application link will continue to work. Upgrading your link may simplify link configuration and make additional authentication protocols available (as mentioned above).
To upgrade an application link when your remote application has been upgraded to include Application Links:
Screenshot above: Upgrading an application link for remote application
Screenshot above: Upgrading an application link wizard
Adding an Application Link
Configuring Authentication for an Application Link