Filtering unused custom fields

Which custom fields are exported?

Project Configurator exports configuration objects that are used directly or indirectly by the exported project(s). As any field configuration in JIRA contains all system and custom fields and every project uses at least one field configuration, the previous rule means that all custom fields will be exported.

However, this is not always convenient. If the original instance has many custom fields, this could make the load into another instance innecesarily complex and increase the risk of unexpected effects on other projects. So the plugin offers options for those JIRA admins that wish to export only those custom fields that are used by the project configuration (see How to use it), excluding the rest of custom fields from the export file.

 

The plugin will consider a custom field as "used" by a project if:

It is used in any of the project's permission, notification or issue security scheme

OR

It is used in any workflow used by the project

OR

(It is visible in at least one field configuration used by the project

AND

It is included in at least one screen used by the project)

OR

It has a value set in any of the issues of the project

The part related to field configurations and screens could be summed up as "users of the project can see this custom field in a screen".

 

Custom fields used in dashboard gadgets

If you are exporting dasboards and a gadget is exported that uses a given custom field (for example it is one of the fields included in the columns for the "Assigned to me" gadget), this custom field will be included in the export, regardless it is used by a exported project or not.