These items are not covered by this app:
Since v1.0.8 the app can export and load custom fields with duplicate field names as long as they have different types. The custom field type is identified by its key, including the app key, as in "com.atlassian.Jira.plugin.system.customfieldtypes:datepicker". This means that several custom fields in the same instance with the same name and type will not be handled correctly. During export, they will be treated as if they were a single custom field. When importing, if the app finds more than one custom field in the target instance with the same name and type impacted by the new configuration, it will stop the import with a message like this:
As the app would be unable to resolve which of those custom fields must receive the new configuration.
These settings impact the presence of some system fields and whether some attributes of a project are mandatory or not. If they are different in the source and destination instance, the exported configuration may be invalid in the target instance.
Import of complete projects (i.e their configuration, issue data and attachments) is subject to the restrictions described Atlassian's Restoring a Project From Backup page, especially:
Currently, data transfer is supported for these applications:
Data of any app that implements the extension points defined in Atlassian's Extending the Jira Import Plugin page will also be handled. Also, any custom field values belonging to custom fields whose types are defined in an app will be imported if that custom field type implements the interface "com.atlassian.jira.imports.project.customfield.ProjectImportableCustomField".
The app supports conditions, validators and post-functions defined in standard Jira plus the following apps: