Bug fixed in recent versions of Jira
Please note, that according to JRASERVER-65734, the bug causing this issue has been fixed in recent versions of Jira. For example, those importing into Jira 7.11.0 or newer should not be affected by this issue.
Sometimes you will see this error:
The custom field 'XXXX ' requires option 'YYYY' for the import but it does not exist in the current JIRA instance
You check the configuration for custom field 'XXXX' at the destination instance and option 'YYYY' is there! This may be caused by JRASERVER-63226, which is explained with greater technical detail in issue JRASERVER-65734. We will explain here a workaround that does not require changing the source database, but only the exported zip file, so it should be more convenient to use in most cases.
Run these queries at the source database:
The first shows you the impacted custom field configuration (whose name usually contains a reference to the custom field name). The second query shows impacted options. If both custom field names and impacted options coincide with the ones shown in the error messages, then you have confirmed this issue.
Paste the following code into the Script Console and click Run
Create a new text file called "CustomFieldOptionEntitiesFixer.groovy" and paste the following script into it:
Open a terminal in the same folder where the script file is located and execute the following command: