Hi,
Using JCMA, I’m trying to migrate one JSM project and one JSM application from my local Data Center to the Cloud.
Every time the Pre-migration check shows the following error:
I don't select Assets at the 'Choose' step:
Does it mean that I can't migrate JSM project until I have Jira Premium on the Cloud side? Or is it a bug?
If you're not migrating any schemas there should be no need to upgrade to JSM Premium on Cloud.
Does this error actually block you from proceeding?
Yes, I can't proceed with this error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've also:
-tried to reinstall the JCMA,
-asked my colleague to check this on their end (also on the environment without asstests at all) - same result
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok that's definitely a bug.
I found the report on [MIG-2478] with Assets migration GA, JCMA preflight check blocks the migration if JSM premium is not activated on target cloud - Create and track feature requests for Atlassian products.
There are 3 workarounds on the ticket:
So you could start a trial of JSM Premium and revert to standard after the migration. It's probably the easiest way.
Or look into the 2 other options.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you use Premium as Trial and then switch down after migration?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Christof
Yes that should work. It is one of the workarounds in MIG-2478
See my comment below.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
that was my fallback plan; however, I wanted to make sure whether this behavior is expected or if it’s a bug
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.