How to uninstall the bundled Jira Cloud Migration Assistant (JCMA) App
Platform Notice: Data Center Only - This article only applies to Atlassian apps 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 Jira Cloud Migration Assistant (JCMA) app is bundled with Jira version 8.14 and above. As a result, it is not possible to uninstall it via the Universal Plugin Manager interface (Jira Admin → Manage Apps). The app can be upgraded to a newer version, and that newer version can be uninstalled, but the bundled version can't be uninstalled.
A Jira Administrator may wish to remove this app for some reason.
Solution
Delete the file JIRA_INSTALL/atlassian-jira/WEB-INF/atlassian-bundled-plugins/jira-migration-plugin-n.n.n.jar, where n.n.n is the version number of the bundled JCMA plugin
Restart the Jira service
Repeat steps 1-2 for each Jira node in the cluster (if Jira Data Center)
After the restart, check that JCMA no longer appears under Manage apps on any node
The steps above involve modifying Jira outside its default configuration. While we have validated that there is no negative impact on all versions of Jira 7 and Jira 8 up to Jira 8.20.5, it's possible this is not the case in future versions of Jira.
For this reason, we recommend that you take due diligence, perform the procedure in a non-prod environment and check for any negative effect on Jira. Checking the atlassian-jira.log file for references to com.atlassian.jira.migration.jira-migration-plugin is a good way to determine whether there has been a negative interaction after removing this app.
Atlassian Support is not able to provide further guidance or support for this procedure
Because it ships bundled, a future Jira upgrade may re-add the JAR. Repeat the above steps after upgrades if you need to keep it out.
Was this helpful?