Migrate server to cloud, issues missing after migration

[Tom Emerson]

We're running a test migration of three representative projects, from server to cloud, working to determine the scope of work prior to starting the main migration project.

The Jira server uses JMWE, cloud migration fails unless we remove this first, we anticipate a fair amount of work at cloud to replace the functionality provided by JMEW.

All three migrations were successful using the cloud migration app/tool.

Looking at the downloadable migration reports, all issues were migrated.

Two of the projects do not display any issues.

At first this appeared to be a permission issue, for example, my "Org & Site Admin" account was not a member of the User group, adding the group to my account did not resolve the issue.  Same for another "Site Admin."

I've read advice that "Site Admin" accounts cannot see or use issues, can only manage the site, other advice is to add the User group to the account to solve the problem.

This initial proof of concept and requirements gathering is using the free tier, is free tier unable to accommodate this scenario? 

[Walter Buggenhout · Accepted solution]

Hi @Tom Emerson,

What you describe seems to point very much towards permissions, if you ask me. You need browse project permission in those projects in order to see the issues, as well ass product access to Jira Software. The first is part of project permissions, the second is part of site admin settings (user management).

Check if both are ok. And also - if you are testing out migration and plan to move to a standard or premium plan later on, do test your migration against those plans instead of the free plan. Permissions configuration in the free plan is limited.

If - after checking out the browse project permission and product access - you still can't see your issues appear, reach out to migration support - they are there to help you look into the details of your migration and help you fix any issues that require intervention from the backend - if necessary.

Hope this helps! 

[Tom Emerson]

We agree (reviewed with our migration team this morning.)
Likely we have "interesting" permissions on those projects at Jira Server.
Next step, we plan to try to identify what these are at Server, then re-run migration.

Either way, this is migrating to the cloud, just need to identify scope and effort before forging ahead with the full migration.

Thank you!