Cloud Migration assistant didn't import issues

[Sahan Pitigala]

I'm testing out migrating from JIRA server to JIRA cloud and I used the Cloud Migration Assitant tool. The migration ran successfully on the server, but only seems to have migrated users and other things such as labels, components, permission schemes, etc. However, the issues appear to be missing.

[Petter Gonçalves]

Hello @Sahan Pitigala

Thank you for reaching out.

It's a really weird behavior that your Cloud Migration Assistant is not migrating any issues. It should include the issues in the import together with all the system fields, as described in the documentation below:

What gets migrated with the Jira Cloud Migration Assistant 

That being said, please follow the steps below to troubleshoot what might be causing the problem:

1. Check if the project related to the issues were archived in the Server instance at the time you executed the Jira Cloud Migration Assistant
2. Check if the project type was Service Desk
3. Check if you used the correct version of the Cloud Migration Assistant, based in your Jira Core version:
   Version history 
   
4. Confirm if you have the proper permissions to browse projects in your Cloud site (Under Project settings > Permissions > Browse project)
5. Check if there are any security level that might be applied to the new issues of the project (Under project settings > Issue Security), adding your user to all the security levels

Let us know if this information helps.

[Sahan Pitigala]

Hi @Petter Gonçalves Sorry about the late reply here. I did not see a notification come in for your response.

1. The project is not archived.

2. Project type is not service desk.

3. We are running JIRA server 8.7 with the latest version of the migration assistant plug-in, which should be compatible.

4. Browser project permission is set to 

Project role
    - atlassian-addons-project-access
    - Users

I've also set myself as the project lead.

5. currently there are no Issue security schemes configured.

[Sahan Pitigala]

@Petter Gonçalves circling back on this.

[JAGE]

@Sahan Pitigala make sure that your user is added to the project after import, if this relation is not created per default.
Fixed it for me