Hi everyone 👋
We’re testing a new prototype that helps you check the compatibility of your installed apps before you upgrade your Data Center product – and we’d love your input!
💡 The idea is simple:
Before upgrading , you can run this tool to see whether your custom apps or Marketplace apps are compatible with your target version and flags the incompatibilities, if any. It gives you helpful info like:
Which apps may break or need updates ⚠️
Technical issues/incompatibilities (for custom apps) and what to do to fix them (migration guides) 🛠️
Incompatibilities in marketplace apps, including the supported versions 📦
Whether you're managing internal/custom apps, or third-party Marketplace apps or both, this aims to save you time and give you more confidence during upgrades.
This solution will also work for air-gapped /offline environments, with one small change — you’ll need to upload the product manifest to see the results. We’re still figuring out the exact details, but our goal is to make sure this works well for air-gapped instances too.
Please take a few minutes to watch this short Loom recording showing how the tool works.
Note : Do note that this is a very early-stage prototype.
We are still deciding where this tool should live — whether it should be part of the Pre-upgrade planner, inside the Universal Plugin Manager (UPM), or available as a separate app that customers can download from the Marketplace or access in some other way.
What features or enhancements would you want to see added?
Would you prefer this tool to live in App management (UPM), Pre-upgrade planner, or somewhere else?
Would this help more with custom apps, Marketplace apps, or both?
How much time or effort would a tool like this save you?
Where do you think is the best place for this tool to live?
Note : Just to clarify, the new App Compatibility Checker is different from the Jira/Confluence update check in UPM (Universal Plugin Manager). Today, the check in UPM mostly shows compatibility info based on what the Marketplace partner has marked — meaning, if the partner says the app is compatible, it shows as compatible.
However, this new prototype goes one step further. It looks at the actual app code to find any technical issues. So even if an app is marked as compatible by the partner, this tool can still flag issues in the code. We believe this deeper check will be helpful for both customers and Marketplace partners — it adds an extra layer of confidence by catching things earlier.
💬 Please leave your feedback either:
In the comments on this post
Or directly on the Loom recording
This is just the first step in solving app compatibility – especially helping you understand compatibility issues. We're also exploring how we might make app testing easier in future phases.
Thanks in advance for your time and input 🙏
@Namita -Thanks for the feedback! Just curious—how many custom apps do you have, if you’re comfortable sharing?
Not really useful for offline instances... So maybe make a online portal where I can upload an exported plain text (so we can check what's being uploaded) config file containing all the app versions we have installed.
Thanks for the feedback @Sake — this is really helpful. As shown in the prototype, we’re also thinking about how to support air-gapped instances. This is definitely a use case we plan to solve. One idea, as mentioned in the prototype, is to let users upload a manifest file so we can run a scan on it.
Hi, this is a really great idea, yesterday I had a problem in the update process, with problems of incomptibilities of an app. As a result i had to roll-back, because the app was a must have. Great for planning the update process, and for selection of the best version. Hope you offer it for productional use soon.....
Thanks for the feedback! We’ve heard similar stories from other customers too — they ran into app issues and had to roll back. We’re hoping this solution will help avoid that. We’ll update the public roadmap once we have a timeline.
This looks good. One suggestion here, for marketplace apps, it should specify what exact versions are compatible with the target Jira version. There could be multiple available versions. For example, if we're on a very old version of the app and since then the app vendor have released multiple versions compatible with target Jira version, it's crucial for an enterprise admin to quickly know how many of such versions are there and review release notes to see what changes are there in each of those versions. From our experience as an marketplace partner , customers often test new app versions on their test instance before upgrading them on the production instance. Knowing how many compatible versions are available, along with direct links to their release notes, would greatly assist in making an informed decision.
@Sujeet Pathak - Thanks for the feedback! We really hear your use case and appreciate you sharing it. We’ll definitely look into which parts we can include.
Hi,
May I know from which Jira and Confluence DC version this feature is available?
@Vinay Shekar S - We’ll update the public roadmap once we have a timeline.