This is the look of this page since version 1.5. For older versions, have a look here.
If you have clicked the "Advanced export" link in the project summary page, or you have chosen to export all projects, you will be taken to this page:
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 on the Filtering Unused Custom Fields page.
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 the 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.
Finally, the "Project XXX configuration export" launches the export with the selected options ("XXX" will be the project key).
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: