Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-63226

Project Import blocked with an error indicating missing custom field option values for Select List custom field types

XMLWordPrintable

    • 7.01
    • 103
    • Severity 2 - Major
    • 49
    • Hide
      Atlassian Update – 13 June 2023

      Dear Customers,

      Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Jira features that solve problems for a greater customer base. To that end, we aim to keep our issues up-to-date so they accurately reflect current customer needs. Based on the impact, we’ve decided to move this issue to our short-term backlog.

      The workaround for this bug is as follows: There is no direct workaround available for this issue so far.

      Please continue watching this ticket for future updates and changes in the timeline that impacts your work.

      Best regards,

      Jakub Cegiel
      Jira DC Quality Engineering

      Show
      Atlassian Update – 13 June 2023 Dear Customers, Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Jira features that solve problems for a greater customer base. To that end, we aim to keep our issues up-to-date so they accurately reflect current customer needs. Based on the impact, we’ve decided to move this issue to our short-term backlog. The workaround for this bug is as follows: There is no direct workaround available for this issue so far. Please continue watching this ticket for future updates and changes in the timeline that impacts your work. Best regards, Jakub Cegiel Jira DC Quality Engineering

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      Summary

      Unable to proceed with Project Import due to errors on Custom Field Options. Example:

      The custom field 'Environment' requires option 'Staging' for the import but it does not exist in the current JIRA instance.

      Steps to Reproduce

      1. Have a source instance that has a Select List Custom Field (single choice) with one or more contexts and options
      2. Configure the same custom field in a target instance with the same contexts and custom field options
      3. Perform Project Import from source to target, using XML backup from source
      4. The import is blocked in certain cases

      Expected Results

      Every project import will go fine

      Actual Results

      In certain cases, it's not possible to proceed with the import. The below can be seen in the GUI under Custom Fields validation:

      The custom field 'Environment' requires option 'Staging' for the import but it does not exist in the current JIRA instance.

      Notes

      One of the causes is when fieldconfiguration.id does not match fieldconfigscheme.id. By rights JIRA should use fieldconfiguration.id when looking up customfieldoption.customfieldconfig, but it incorrectly uses fieldconfigscheme.id, causing the problem. More details can be found in JRASERVER-65734.

      Workaround

      Refer to Project Import fails due to missing Custom Field Options for the above problem.

              Unassigned Unassigned
              znoorsazali Zul NS [Atlassian]
              Votes:
              81 Vote for this issue
              Watchers:
              82 Start watching this issue

                Created:
                Updated: