While restoring the Jira instance I have such error:
Error importing data: java.lang.IllegalArgumentException: [GenericDelegator.makeValue] could not find entity for entityName: AdHocUpgradeTaskHistory
What is the reason?
I moved our only next-gen project to a classic project and then made a cloud to server backup - it failed to import with this error. Seems there is nothing that can be done.
Hi Толмачев,
Another possible reason to the error is that the backup files are generated for JIRA Cloud to Cloud migration rather than a Cloud to Server migration.
If you have next-gen projects on the JIRA Cloud instance, it may prohibits you to create backup for Server.
Jira Cloud products are regularly updated with the absolute latest features and improvements. They run on completely different branches of development than the latest downloadable version of Jira Server or Jira Data Center products. Some of these features are incompatible between cloud and server products.
Next-gen projects, for example, do not exist in Jira Server or Jira Data Center. To create a usable server backup, you need to delete all next-gen projects from your Jira Cloud site. Learn more about next-gen projects.
We recommend moving important issues from these projects into server-supported project templates (those administered by schemes). To do so:
Jira lists all your next-gen projects, links to filters that contain those projects' issues, and information about the project's owner to help you investigate what issues you may want to keep in your backup.
You can also delete all next-gen projects outright. To do so:
Regards,
Kelly
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @KellyW
This is very good to know, thank you. I hope you guys are making a KB out of this answer. :)
This however means Jira Cloud project import becomes even more crucial than ever since cloud and server instances are drifting apart. For example in our case, we would like to use server instance as intermediate system while combining several Jira instances into one (since Jira Cloud project import is not possible) (migration from cloud to cloud). Now that option is also out of question (because teams are bound to start using next-gen projects in future). That leaves us with only CSV export/import to handle this.
Basically this situation makes following documentation obsolete:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Толмачев Станислав Юрьевич
This link has a solution for the error you're experiencing.
Could not find entity for entityName - when restoring a XML backup into a JIRA application
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.