Problem
If the user cannot see the issues after migrating the project from the server/dc to the cloud.
Solution
In Jira Cloud, one condition is necessary and sufficient for a user to view a project's issues. The user must have the “Browse Project” permission in the Permission Scheme assigned to the respective project. Even if a user is an administrator, he cannot see the project issues if he doesn’t have the “Browse Project” permission in the respective permission scheme.
Using the account used for the migration also doesn’t guarantee that the user will have the necessary permissions.
The course of action on Jira Cloud is as follows:
Log in with a user that has permission to edit permission schemes. An administrator user should work.
Identify and edit the permission scheme assigned to the migrated project.
Give “Browse Project” permission to the users/groups/roles that should be able to see the project issues.
Note: If a user with a given mail on the server has permission to view the project, and on the cloud the user with the same mail does not, a possible reason may be that the “Browse Project” permission on the server is given to a Group that the user is a member of. On the cloud, we create groups but do not populate them with users because of the way Jira manages groups.