Unable to see issues after migration using Configuration Manager for Jira app from Server/DC to Cloud

Owned by Vijaya Durga Vempa
Last updated: Apr 26, 2024
1 min read

Problem

Users cannot see the issues after migrating a 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 does not have the “Browse Project” permission in the respective permission scheme.

Using the account used for the migration also does not guarantee that the user will have the necessary permissions.

The course of action on Jira Cloud is as follows:

  1. Log in with a user that has permission to edit permission schemes. An administrator user should work.

  2. Identify and edit the permission scheme assigned to the migrated project.

  3. Give “Browse Project” permission to the users/groups/roles that should be able to see the project issues.

If a user has permission to view the project on the server with a specific email address but cannot view the issue on the cloud with the same email address, it could be that on the server, the "Browse Project" permission granted to a group the user belongs to. On the other hand, on the cloud, CMJ will only create empty groups without users.