Automation for Jira: Incompatibility During Jira 10.x Upgrade Check
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
The Automation for Jira (A4J) application is flagged as “Incompatible” during Jira update check for an upgrade from Jira 9.x to Jira 10.x.
The Jira update check page can be accessed from
⚙ > Applications > Plan your upgrade > Jira update check
or
⚙ > Manage Apps > Jira update check.
Diagnosis
The above issue is observed during Jira update check for an upgrade from Jira 9.x to Jira 10.x, particularly when Automation for Jira has been upgraded from its bundled / pre-installed version.
The root cause and solution are applicable to the following versions.
Installed Jira version: 9.x
Check compatibility for an update to: 10.x or any higher version
Cause
Starting with Jira 10.0, Automation for Jira is no longer published on the Atlassian Marketplace and is only included as a bundled plugin within Jira. Refer to Jira 10.0 release notes for more details.
Due to this change, the compatible version of the application for Jira 10.x is not found on the Marketplace during the update check from Jira 9.x to Jira 10.x, causing it to be marked as incompatible.
Solution
The incompatible warning for Automation for Jira can be safely ignored. The application remains compatible with Jira 10.x and higher versions and is bundled within Jira itself. It will continue to function properly after upgrading Jira, and no additional actions are required.
Was this helpful?