Preventing Errors

The most reliable way to ensure that your export and import processes run smoothly is to understand how your configurations and project data are handled, and that you follow our recommended best practices which are included in our quick reference Project Configurator Checklist. Also, note that Project Configurator’s default export and import options are applicable to the majority of user scenarios.

The following sections provide links to our Project Configurator Knowledge Base articles related to a few common export and import errors. If you’re having issues with errors or warnings and do not know how to resolve them, refer to these pages for solutions.

If Project Configurator returns any additional errors, and you need help resolving them, you can search the Knowledge Base for other how-tos and troubleshooting articles. If troubles persist, please submit a request through our support portal where our Support team will be happy to assist you.

Configuration export errors

Project Configurator expects to export a valid configuration in Jira. Inconsistencies in the original configuration of your instance may cause the export process to finish with an error instead of generating the expected XML file. The Object Dependencies report provides a visual mapping of how objects are used or referenced by other objects in your instance. Running this report before an export helps you identify any potential issues and take appropriate action before generating the export file. This knowledge base article describes some common causes of errors in export files.

Configuration import errors

There are a few common configuration import errors that you may encounter when trying to import configurations. Understanding how Project Configurator handles configurations and its limitations will help you in preventing these errors from the start. You should also ensure that potential related exporting errors are resolved.

Project import errors

This knowledge base article helps you anticipate potential migration issues or resolve them if they do occur. Consider that the full migration process includes a step where the source configuration file is imported to the target instance. Our exporting or importing configurations errors pages may therefore also be useful even when you are migrating complete projects.

Always run a simulated import before applying configuration changes to your target instance. It provides an overview of the changes that will be applied to the target, included the objects that will be created or modified as well as warnings and any changes resulting in errors. This gives you the opportunity to refine the content of your import before committing any changes.