On this page:
|
Handling complete projects
When exporting or importing complete projects (i.e., their configuration, issue data, and attachments), the XML backup excludes data for projects that are not exported.
...
Export and import of complete projects are always done in two steps: first configuration, then data and attachments. This becomes more evident if the configuration step fails for any reason. In that case, the data step will not be performed. When performing an import, you should always select to option to run a simulated configuration import to assess the possible impact of the configuration changes on other projects in the target instance.
Project Configurator uses the Restore Project from XML Backup feature, therefore inheriting some of its limitations and strengths.
Object identification
To identify corresponding objects across different instances of Jira, Project Configurator relies on the name of the objects, with the following exceptions:
...
The object context is also considered for those objects that are part of (or are children of) other objects. For example, options are identified by their name only among the options existing within a custom field configuration.
Minimum changes on import
When importing a configuration, Project Configurator applies the minimum set of changes to make the configuration in Jira equivalent to the configuration described in the XML file. This means the following:
...
When an object has a set of dependent objects, Project Configurator will perform the minimum number of removals and additions in the dependents so that the final set of dependent objects in Jira is equivalent to the set in the XML file.
Selection of objects to export
When exporting a project configuration to XML, Project Configurator exports the project configuration, including the following:
...