Follow the guidance in this section to ensure that your configuration and project imports run smoothly.
| Excerpt | ||
|---|---|---|
| ||
| Everything you need to know about importing configuration changes and project data including best practices and a guide to import options. |
On this page:
|
Safety measures
Importing either a configuration file or a set of projects and their data could change several things in your target Jira configuration, including global objects such as schemes, workflows, or custom fields that may be used by other projects. We recommended recommend that you follow the safety measures below.
...
Make a full backup of the database. If importing complete projects, also consider backing up the attachments since the import will add attachments for any new projects being imported. You can make a backup using Jira’s built-in XML importer located under under System Settings on on your Jira Administration page.
Note any Project Configurator limitations that apply to your configuration changes or project data migrations.
Run an an Import Simulation against against the intended import file, then verify that the import will do what you expect.
Perform the import on a test instance before applying your changes to a live environment.
...
After importing configuration changes (the XML file), it is highly recommended that you reindex your database. This is not required if importing complete projects since the data import stage automatically launches a reindex.
...
If you import complete projects, your instance will be locked for a period of time, depending on the size of the import. The larger the amount of data, the longer the process takes. Limit disruption to your users by performing the migration outside of office hours when possible and announce the planned downtime in advance.
...
Deploying configuration changes, importing projects from another instance, or merging instances of Jira may, in some cases, be complex tasks. Your chances of success will be much higher if you follow a defined and tested process. We also recommend that you refer to the the Project Configurator Checklist as as a quick reminder of our prerequisites and best practices before proceeding with any migration process.
...
On successful loading of an import file, Project Configurator clears the temporary export files saved in the temp directory, <JiraInstallDirectory>/temp. If the import process fails, to save space on your local disk, manually clear these files before generating another export file.
| Tip |
|---|
See Project Configurator’s Configurator’s import options to to learn how you can safely customize the import settings. |
...