Import Options

The Import Options section is available at Step 1: Configure Import when a workflow is selected.

Define your own settings to execute an import:

Import Strategy

To update custom field contexts, screens and issue type screen schemes check if the entities that should be imported would be merged with the existing ones or re-created. The default value is Merge for all three entities.

Issue Types

Choose issue types that should be imported when import the workflow from the issue types select list. 

The contexts of the custom fields that are not related to Any issue type, are partially imported according to the selected issue types. Only custom fields that have at least one of the selected issue types related to the context or that have global context, and only the relevant issue type screen schemes relations for the selected issue types are imported. The default value is Any Issue Type.

Projects Mapping

You can define a mapping between a project from the imported kiwi file and a project from the Jira Import server. This is especially useful when the same project has different keys on the export and import server.

The projects that can be mapped are the projects that are used in the contexts of the exported custom fields. By default the projects are mapped by their key. If the corresponding key can not be found on the Import server, the Source Project Key is marked with the red color (MARPRJ in the picture below) and  the corresponding value in the column Mapped Project Key is by default Find By Key. This means the project key is searched again when the import is executed. It is possible in the meantime the project is created, for instance by a pre-import sil script.

You can change the mapping for a project by clicking the Change link.

Choose one of the existing values from the Import server.

If choose the None value, the corresponding source project is ignored from the custom field contexts where it appears.

If the mapped project key for a source project key is None or can not be found at the import execution time, the project is ignored from the custom field contexts where it is used. When trying to create a custom field context, if no associated project key is found the context is not created any more.

Publish active workflows

If the workflow that you are trying to import exists and is active on the Jira Import server, a draft is created for the imported workflow. If you want to automatically publish this draft, change the value of the radio 'For active workflows a draft is created. Do you want to publish it?' to Yes.

If the default value(No) is selected, only the draft is created(or updated if the draft exists) and it needs to be manually published.