-
Bug
-
Resolution: Fixed
-
Low
-
None
-
None
-
None
-
Minor
Issue Summary
Apps that have only a Data Center and Cloud listing in Marketplace do not appear correctly in App Assessment for Exists in Cloud and Can Be Migrated columns, even if the data is correct in Marketplace.
Here we can see the app app.jxl has an entry in Maketplace for the /migration endpoint.
$ curl --silent 'https://marketplace.atlassian.com/rest/2/addons/app.jxl/migration' | jq '.' { "vendorId": 1219648, "addonKey": "app.jxl", "addonName": "JXL - Spreadsheet Table Issue Editor for Jira", "cloudAddonKey": "app.jxl", "cloudVersionAvailability": "PUBLIC", "cloudVersionDevelopmentRoadmap": "https://jxl.app/docs/roadmap", "featureDifferenceDocumentation": "https://jxl.app/help/migration/features", "migrationDocumentation": "https://jxl.app/help/migration/paths", "cloudMigrationAssistantCompatibility": "1.0.0" }
We can confirm the versions available with
$ curl --silent 'https://marketplace.atlassian.com/rest/2/addons/app.jxl?application=jira&hosting=datacenter&withVersion=true' | jq '._embedded.version.deployment' { "server": false, "cloud": false, "connect": false, "autoUpdateAllowed": false, "permissions": [], "dataCenter": true, "dataCenterStatus": "compatible" }
However in the Cloud Migration Assistants, they only uses hosting=server, and doesn't check the datacenter value for hosting when aggregating the marketplace data.
Steps to Reproduce
- In Marketplace have an app that only has DataCenter and Cloud entries
- Install the app in a Data Center instance of Jira or Confluence
- Go to App Assessment in the relevant CMA and check the values for Exists in cloud and Can be migrated
Expected Results
Exists in cloud and Can be migrated are correctly populated based on the information in https://developer.atlassian.com/platform/app-migration/app-assessment-UI/ .
Actual Results
Exists in cloud and Can be migrated show as 
.
Workaround
Ensure you app has an entry for server in Marketplace.
- is related to
-
MOVE-84900 Loading...
-
- relates to
-
[MIG-814] Apps with only Data Center and Cloud versions do not appear with correct data in App Assessment
Hi Team,
With the release of CCMA 3.3.1 this issue is now resolved for both JCMA and CCMA. Please ensure you have updated to the latest version.
Regards,
James.
Hi James and David. I can confirm our app is now listed with icon and tick marks.
The "Can be migrated" check now has a grey "Stage 1" tick for "unknown or low migration success", which imho is an unnecessarily vendor hostile assessment. I mean what is it, unknown or low? Understandable that you want to indicate either/both to customers but why mix them like this? I can't imagine a technical reason. But this is a separate issue I guess.
Hello Team,
With the recent release of JCMA 1.6.5 this issue has now been resolved in Jira. This issue will be for CCMA in the next release.
Regards,
James.
Update - Date of release
The fix will be released in JCMA v1.6.4, on November 10th.
David Almeida,
Engineering Manager, Atlassian Cloud Migrations
Hi 21e8e5fc380a,
Unfortunately, we can't enable JXL for Server.
We've found the cause of the bug and will release a fix in the coming weeks.
Best regards,
David Almeida.
Hi folks,
as a quick fix, can you just enable JXL for Server?
Thank you very much,
- H
YOU ARE SPREADING MISINFORMATION ABOUT THE AVAILABILITY OF OUR APP AND ITS MIGRATION CAPABILITIES. WHEN DO YOU INTEND TO ADDRESS THIS?
I can only repeat what Daniel said. This is a critical issue to us, as the App Assessment actively suggests users to move away from JXL, when instead JXL is really a prime example for an app that can be migrated from DC to Cloud with zero pain. I'd hope that this is addressed with highest priority.
Please also note that JXL is, of course, perfectly compatible with Server. We'd be more than happy to have JXL available for Server, if you folks can enable this for us.
Hi team,
Dan here from JXL. I had originally reported this, so we're affected by this obviously. The prio "Low" and status "Gathering impact" is worrying me. Isn't this a clear bug that should be addressed asap even if it only affected a handful of app vendors (and customers)?
Btw we'd be happy to offer a Server app as well, it's ready and apparently that would fix this problem. It's just that we're not allowed to anymore. So we're forced into this bug now.
Any chance you could give us a rough estimate for this?
Thanks!
Hi 74700d9b524c - Good to hear from you. Sorry about the trouble you experienced with the App Assessment table earlier. Glad we were able to get it fixed! Perhaps I can shed some light on the labeling system. We've combined labels for "unknown" and "low" migration success rates under a single label ("Stage 1") because it reduces complexity for our customers in understanding what the labels mean and how they should proceed. In both scenarios, where the migration success rate is "unknown" or "low" we recommend that our customers proceed with caution (meaning thoroughly test the migration path). It is not meant to be an assessment of the app, nor the vendor. Please let us know if any of your customers have understood otherwise, so that we can help sort it out.
Thanks,
akassab
Product Manager, Atlassian Cloud Migrations