On this page:
|
Selecting projects
The first stage of compiling an export file is to select which projects to export and whether to export complete projects or only their configurations.
...
In your source instance, select Manage Apps from the Jira Administration menu then select Export Projects under Project Configurator in the left sidebar. This displays the Export Projects screen.
Select one or more projects from the Projects to Export drop-down list or select the Export All Projects checkbox to export all of your projects.
Select the Export mode. Options include Configuration Only or Complete Project. This selection applies to all of the selected projects.
Options
The Export Projects screen displays default options depending on whether you select Configuration Only or Complete Projects. If you wish to define your own custom options, you can then save this configuration to use in subsequent export tasks. This means you only need to select the saved configuration name from the Configuration Options drop-down list and not manually define each option.
...
Export Filename
The system generates a default filename for you, but you can change it to suit your needs by typing a name in the Export Filename input field. Note that file names must be unique.
...
Automatic: Project Configurator embeds all necessary attachments for the selected projects into the same ZIP file that contains the project configuration and data.
Manual: This is recommended for larger instances with several issues and attachments. The exported ZIP file will not contain any attachments. You will need to move them manually to the target server before importing the projects. Our knowledge base article on manual attachment migration provides more information about this process.
Custom
...
field options
The Filtering Custom Fieldsfiltering custom fields option allows you to select whether to export all custom fields or only those that are used by the exported projects (default). If you select Only those used in projects (no values considered), this exports only custom fields used by the exported projects, but it ignores whether there are values set for those fields in issues of the exported projects.
Users and
...
groups
The User Options drop-down list allows you to select how to handle user data during the export. Available options are:
...
The Group Options drop-down list offers the same options as User Options: Full Export, Ignore Invalid Groups, and Do Not Export. Currently the only case detected as an "invalid" group is when a group cannot be found for a given name.
Filters and
...
dashboards
The Filters To Export drop-down list allows you to control the export of filters. The choices are:
...
The Dashboards To Export drop-down list offers the same choices as the Filters To Export listed above. Take into account that if you choose to export some or all dashboards but none of the filters, those filters that are used from dashboards will be exported anyway so that the exported configuration is complete.
Software
...
boards
Agile Board Options acts in a similar way. It allows you to select which boards to include in the export. The available options are:
...
| Tip |
|---|
Export of software boards requires that Jira Software application is enabled, otherwise, no boards are exported. |
Saving export options
To save a custom export configuration to use in subsequent export tasks, complete the following steps:
Before running the export, click Save Configuration.
In the corresponding pop-up window, enter a name for the export configuration that you can easily identify for future use, e.g., config-only-prod. Names must be unique.
To use the saved configuration, select it from the Configuration Options drop-down list that appears at the top of the Export Projects screen.
If you wish to delete a selected saved configuration, click the Trash icon next to the Configuration Options drop-down list.
Run the export
Once you have selected your projects and configured your export options, click Export Projects. A progress indicator is displayed. Once complete, a success message is displayed. You can then download and save the corresponding .xml or .zip file.
What happens when I import this configuration file?
When you import a configuration file created with "Ignore invalid …" or "Do not export" options, it is likely that it contains references to users or groups (by their names) where those users or groups are not included in the corresponding section of the configuration file. If a user or group with that name does not already exist in the target instance, there are some implications:
...