Hi everyone,
Based on your inputs on this post:
Help us improve the App compatibility checker – We need your feedback!
We’re opening up the App compatibility scanner in an open beta starting April 20 to help Jira and Confluence Data Center admins check their apps before upgrading.
This post shares what the tool is, who it’s for, key benefits, how to get started, and how to give feedback.
What is the App compatibility scanner?
The App compatibility scanner is a tool designed to help Jira and Confluence admins quickly check whether their installed apps, especially custom (in‑house) apps, are compatible with upcoming Data Center versions and understand the details of any incompatibilities.
Note: This is still work in progress and focused on a specific set of versions and checks. It’s already useful today, but it might not cover 100% of use cases yet as we continue to expand coverage based on your feedback.
Who is this for?
This open beta is intended for:
-
Jira and Confluence Data Center admins
-
Customers with custom (in‑house) apps
-
Teams planning upgrades along the supported LTS versions
-
Customers who can safely test new tools in a non‑production / test environment
What you can do with it today (key benefits)
With the current open beta, you can:
-
See an overview of app compatibility status for your instance
-
Identify incompatible Java APIs used by your custom apps against specific target versions
-
Highlight major dependency updates in custom (in‑house) apps
-
Export scan results in CSV or JSON format to share with developers and architects
Under the hood, the tool currently includes:
-
Marketplace Compatibility Matrix
Checks app compatibility (yes or no) based on vendor‑provided information (Marketplace apps)
-
Java API usage check
Flags incompatible Java APIs in your target versions:
-
Dependency check
Highlights major dependency updates for custom (in‑house) apps
Supported versions and upgrade paths (current scope)
The current beta focuses on specific upgrade paths for Jira and Confluence Data Center.
1. Upgrading from Jira 9.12 / Confluence 8.5 to Jira 10.3 or 11.3 / Confluence 9.2 or 10.2
2. Upgrading from Jira 10.3 / Confluence 9.2 to Jira 11.3 / Confluence 10.2
3. Moving from Jira 9.12 / Confluence 8.5 all the way to Jira 11.3 / Confluence 10.2
If you’re planning a longer upgrade path:
-
Use version 0.1.0 to move from Jira 9.12 / Confluence 8.5 to Jira 10.3 / Confluence 9.2.
-
Then use version 1.0.0 of the app to move from Jira 10.3 / Confluence 9.2 to Jira 11.3 / Confluence 10.2.
Important notes & limitations
We’ll continue to iterate on coverage and experience, so your feedback at this stage is especially valuable.
How to get started (from April 20)
-
Choose a test environment that matches one of the supported source versions.
-
Pick the right download link based on your upgrade path.
-
Install the app on your Jira/Confluence Data Center test instance.
-
Run a scan of your installed apps for your target versions.
-
Review the dashboard and detailed findings for each custom app.
How to share feedback or report issues
Your feedback will shape how this tool evolves. Please leave feedback on the page as comments.
You can tell us:
-
How well the scanner worked for your upgrade scenario
-
Any compatibility issues it helped you catch
-
Where the current scope fell short for your use case