-
Bug
-
Resolution: Invalid
-
Low
-
18
-
Severity 2 - Major
-
1
-
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Summary
Unable to proceed with Project Import due to errors on Custom field options. As an example:
The custom field 'Environment' requires option 'Staging' for the import but it does not exist in the current JIRA instance.
Steps to Reproduce
- Have a source instance that has a Single-select custom field with multiple contexts. (Eg. Environment)
- Set up target instance to have the same contexts and custom field options
- Perform Project Import from the XML backup
- The project import can fail in certain cases
Expected Results
Every project import will go fine
Actual Results
On certain project import, it can fail in certain cases. The below can be seen in the UI under custom field section:
The custom field 'Environment' requires option 'Staging' for the import but it does not exist in the current JIRA instance.
Notes
One of the trigger is when customfieldoption.customfieldconfig does not match fieldconfigscheme.id but the relation relies on fieldconfigschemeissuetype table between fieldconfiguration and its fieldconfigscheme.
Workaround
- is related to
-
JRASERVER-63226 Project Import blocked with an error indicating missing custom field option values for Select List custom field types
- Short Term Backlog