JIRA Documentation

JIRA 6.3 EAP
JIRA 6.0 Documentation
JIRA 5.2 Documentation
JIRA 5.1 Documentation
More...
 

 

Search the Knowledge Base and Documentation Spaces

You're visiting the JIRA Knowledge Base. Visit the JIRA Knowledge Base Home for an overview.

Skip to end of metadata
Go to start of metadata

Symptoms

When trying to project import you hit an on-screen error that looks like the following despite having the same version of JIRA and plugins indicated.

Diagnosis

This usually happens because of inconsistencies in custom fields that plugins might or might not have created in your environments. There is currently a bug ticket for this issue.  JRA-28480 - Project Import fail with Custom Field option not available Awaiting Development

Resolution

Icon

Prior to going through this resolution, please ensure all requirements as listed in our Restoring a Project from Backup documentation have been met.

We will load different sets of data into a separate JIRA instance in order to minimize custom field issues that arise from differences in usage.

Legend

PRD = Production data backup
SRC = Source data backup
STG = Staging data backup

Pre-requisites
  • Have a copy of your <JIRA-home>/plugin/installed-plugins folder from production ready (plugins zip).
  • Have a backup of your production data ready (PRD).
  • Have a backup of your source data (SRC).
Resolution Steps
  1. Install JIRA on a separate staging instance and unpack the plugins zip from your production server in to the same location. We are trying to emulate your production instance.
  2. Import the XML backup from (SRC) to your staging instance.
  3. Make an XML backup of your staging instance, (STG).
  4. Shutdown your staging JIRA instance.
  5. Using the Connecting JIRA to a Database documentation, create a new database for your staging environment and point to it with the Using the JIRA Configuration Tool documentation.
  6. Restart your staging JIRA instance. This will rebuild the database structure, using the new database.
  7. Restore XML on the JIRA staging instance startup using the (PRD) backup.
  8. Import the project from the (STG) backup.
  9. After the (PRD) to staging import is successful, generate another backup (final).
  10. Backup your Production instance.
  11. Import the (final) backup into Production.

Alternative Resolution

Icon

In some cases, after installing the required plugins in the source instance, a restart is required. Then, produce the backup and try the import again. If this does not fix the problem, please see the following.

  1. Get the ID of the problematic custom field in your target JIRA instance (Custom Field > Configure), the ID of that custom field will shown at the end of the URL.
  2. Edit the entities.xml of the backup, search and replace the ID of that custom field with ID retrieve from step 1.
  3. Save the entities.xml after all the changes on the remaining custom field ID if has any.
  4. Perform the project import again using the edited entities.xml.
(info) Thanks to one of our awesome customers who provided the above workaround.

Related Content

 Expand to see related content
Help us improve!
Is this article helpful?
Is the content complete?
Is it well written?

1 Comment

  1. "Edit the entities.xml of the backup, search and replace the ID of that custom field with ID retrieve from step 1."

    Search for what now?