After selecting which projects will be exported, you need to choose wether exporting only the project configurations or complete projects
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_for configuration only exports and
project-dump_for complete exports.
BDI1-ZH19-A0IA-E1XUis the server id of the instance where the export was run
PBis the key of the exported projects. If all projects in the instance are exported, this will be replaced by
ALL. If more than one project but not all of the existing ones are exported, this will be replaced by
XXis the number of projects included in the export (for example
xmlfor configuration only exports and
zipfor complete exports.
This field is exclusive for complete exports.
If you select Automatic, Project Configurator will embed all necessary attachments for the selected projects into the same ZIP that contains the projects configuration and data.
If you select Manual, the exported ZIP will not contain any attachments, and you will need to move them manually to the target server before importing the projects.
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.
"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:
What will happen when I load this configuration file?
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: