After migration to cloud i do not see any issues

[Veiko]

Used cloud migration app on self hosted Jira and report shows that several projects and thousands of issues were migrated.
However in cloud i see projects, but no issues at all under projects.

I have tried adding my user to all possible jira groups on cloud but without any luck. It is especially strange that i don't see issues because it is the same user i used to do the migration!

How to fix the issue?

[Trudy Claspill]

Hello @Veiko 

Welcome to the Atlassian community.

When you configured your migration plan in JCMA, what options did you choose for migrating Users and Groups?

When migrating Projects to Jira Cloud the Permissions Scheme used by the project will also migrate and those Permissions settings will be enforced in Cloud. If you did not migrate Users and Groups, and permissions are allocated to groups or to groups through their association with Project Roles, then your permissions to see the issues would not be available in Cloud.

Review the Permissions Scheme to see how the Browse Projects permission is allocated, and assign your user to the Groups or Roles specified therein.

[Arkadiusz Wroblewski]

Hello and Welcome @Veiko 

I would first suspect permissions/visibility, not that all issues vanished during migration.

The key thing to check is whether your user really has Browse Project / Browse Space permission in those migrated projects, because that permission is what allows users to actually see work items at all. Atlassian documents that directly.

I would also check whether issue security was used in the source project. After migration, that can absolutely lead to “project is visible, but issues are not”. Atlassian has migration KBs around issue-security-related visibility problems as well. 

https://support.atlassian.com/migration/kb/jcma-doesnt-migrate-issue-security-level-permission-with-unsupported-custom-fields/ 

[Ajay _view26_]

Hi @Veiko 

Welcome to the community! 

If the projects are present in Cloud but all issues appear missing, I would first suspect permissions/visibility rather than the migration silently dropping every issue. Atlassian’s migration KBs call out that after migration, issues can appear “missing” when the user does not have Browse Projects permission in the target project, or when issue-level security is in play.