Jira Cloud Migration Error:

[Jonas Hornung]

Hi all,

We have to migrate our Jira Server to the cloud version.

I just did a test migration of one project, but some Issues were not importet.

Could sb. please tell me how we can deal with the following error?

ERROR SYS project-import We couldn't import Issue (..) because of 1 missing dependencies: Custom Field 'Sprint'. This caused 13 other items to fail. Check the reasons for the missing dependencies on your server site.

Thank you so much!

Best,

Jonas Hornung

[fjgonzalez]

Hello @Jonas Hornung

Could you explain how did you fix the error?. We are facing the same probmel :(

Best regards,

Francisco Gonzalez

[Andy Heinzer]

Hi Jonas,

I created a support ticket on your behalf for this problem over in https://getsupport.atlassian.com/servicedesk/customer/portal/49/MOVE-35625

Please refer to that case for additional help with this problem.

Thanks

Andy

[Systems Manager]

We're experiencing the same issue. I tried viewing the ticket in https://getsupport.atlassian.com/servicedesk/customer/portal/49/MOVE-35625 but I'm getting an error that says I do not have permissions to view it even though I'm logged in to our Atlassian account. 

[Andy Heinzer]

@Systems Manager I would not expect you to be able to view that ticket, it is restricted to that user and Atlassian Support.

Reviewing the case, I see that Jonas appears to have found a solution, but it was not clear exactly how he resolved the error in his case.  I would be interested to try to learn more about exactly which method you are using to try to migrate this data.

• Are you using a site-import (from an XML backup zip file)?
• Or are you using the Jira Cloud Migration Assistant?

It has also been suggested to run the Data Integrity Checker against the Jira Server data before trying this migration just in case the data is not in an expected format.  I am also interested to learn more about what version of Jira Software this data is coming from.

Alternatively, anyone looking to migrate from Server to Cloud should still be able to create a support ticket under https://support.atlassian.com/contact/ and then select the Migration Support option.

[fjgonzalez]

Hello @Andy Heinzer

Do you know what was the solution provided by Atlassian in order to fix this error? We are trying to connect with @Jonas Hornung but we haven had an answer yet.

Thanks in advance.

[fjgonzalez]

Hello,

Creating a sprint in the source instance. Having a open sprint in the source instance could fix the error.

Best regards