After selecting which projects will be exported (either complete or only their configuration), you will be taken to this page:


Export filename

At the top, there is a text box where you can specify the name for the exported file. The system will generate a default filename, but you can change it to suit your needs.

The exported file will have a default filename like this config-dump_BDI1-ZH19-A0IA-E1XU_PB.xml where:

Export options

The "Filtering custom fields" options selects whether all custom fields will be exported or only those that are used by the exported project(s). Detailed explanations about the criteria for deciding whether a custom field is "used" by a project can be found here.

The "User export options" is a list that lets you select one way to handle user data during export. Available options are:

"Group export options" offers the same choices for export of groups. Take into account that currently the only case detected as an "invalid" group is when a group cannot be found for a given name.

When you are about to load a configuration file created with "Ignore invalid ..." or "Do not export" options, it is likely that it contains some references to users or groups (by their names) where those users/ groups are not included in the corresponding section of the configuration file. If a user/group with that name does not already exist in the target instance, there are some implications:

  • Except in very rare cases (e.g. users/groups are the default values in a custom field) the load will not fail.
  • However you are creating an inconsistency in your target instance. There will be a project, component, scheme,...using a user name or group name that does not correspond to a valid user/group.


"Filter export options" lets you control export of filters. The choices are:

"Dashboard export options" offers the same choices for export of dashboards. 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.

"Scrum and Kanban boards to export" acts in a similar way. It lets you select which Agile boards will be included in the export. The available options are:

Export of Agile boards requires that JIRA Agile plugin (in JIRA 6) or JIRA Software application (in JIRA 7) are enabled. Otherwise, no Agile board will be exported (even if you requested something else).

Finally, there are two buttons at the bottom that let you either launch the export or go back to the previous step in the export process. If you are exporting complete projects (i,e, their configuration, data and attachments) the export button will be called "Export complete project". If exporting only their configuration, the export button will be called "Export project configuration". As you can see, the same texts will be shown as page title and header.

Next step: viewing export results

.