Version for linked application within Application Links interface is incorrect after linked application is upgraded

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Within Settings > Applications > Application Links within Jira, if there a link to another Atlassian product such as Bitbucket for example, the version of the linked product is listed. After an upgrade of that linked product (Bitbucket in this example), the version listed will be incorrectly showing the older version prior to the upgrade.

(Auto-migrated image: description temporarily unavailable)

Environment

Any Jira environment with Application Links to another Atlassian Product

Cause

This version is populated within the Application Links interface is cached upon initial start up of Jira and the connection to the linked application. So if the linked application is upgraded and restarted but Jira is not, the version will still show the older version because the cache has not been refreshed.

Solution

Restart the Jira instance after upgrading the linked application. After Jira reboots and connects to the upgraded application, the proper version listed will be listed.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.