KIWI™ is the tool that enables users to export or import your workflows in just a few seconds. Designed to satisfy many customers requests, this app offers you the following features:
...
Exports/imports a workflow
KiwiKIWI™ exports and restores the selected workflow, carrying over all the steps, statuses and transitions:
...
If you are using our Power Scripts™ for Jira app and you have created SIL™ scripts (validators, conditions or post functions) on the transitions of the exported workflow, these SIL™ scripts will be exported and restored on the Jira import server.
...
| Note |
|---|
| While importing if on the destination server there is a SIL™ script file having the same name and path with a SIL™ script from the kiwi file that is being imported, the existing SIL™ file will be overwritten. You will receive a warning message in the Import page at Step 2: Actions for the action Create or update the SIL™ files (the action can be found and also disabled in the section General actions). |
...
Exports/imports Issue type screen schemes
KiwiKIWI™ exports/imports the Issue type screen schemes related to the selected workflow.
...
Screen schemes that associate the issue operations to the screens. These screens are also exported/imported by KIWI™, along with the screens used in the workflow for transitions.
...
Exports/imports workflow related screens
KIWI™ exports and imports all the screens used directly in the selected workflow (screens that are configured as Transition View in the workflow transitions), and also all the screens from the Issue type screen schemes the workflow is related to.
...
Exports/imports workflow related issue types
KIWI™ exports all the issue types from the contexts of related custom fields and that are found in the related issue type screen schemes.
Choose issue types to be imported in the import page. Only custom fields that have at least one of the selected issue types associated in their context or that have global context, and only the relevant issue type screen schemes associations for the selected issue types are imported.
| Note |
|---|
Issue Types are mapped by name. Every exported issue type that is selected for import is analyzed, and if it exists on the Jira import instance, found by name it is updated to match the issue type from the exported file otherwise the issue type is created. |
Exports/imports workflow related custom fields
KIWI™ exports/imports all the custom fields from the screens related to the workflow (for instance transition screens and the screens that are found in the related issue type screen schemes).
KIWI™ also exports the custom fields that are not associated directly with the workflow. KIWI™ also carries over all the custom fields that are specific to the Create/Edit/View screens only in the ITSS and not in the workflow.
...
During the import every custom field (let's name it exported cf) that is available in one of the exported screens is mapped by using the following algorithm:
- KIWI™ looks for a mapping/match using the Change action link from the Import page Step 2 or from the mapping file.
- If there is a mapping/match defined in the mapping file, it gets the custom field from the Jira Import instance. The existing custom field is updated to match the exported custom field.
- Otherwise if custom field that has the same name and the same type is found, the existing custom field is updated to match the exported custom field.
- Otherwise the custom field is created.
When a custom field is updated, the name, description, the context(s) and the searcher are updated. KIWI™ also offers you the possibility to change the custom field actions directly from theImport page.
...
Updating or creating a custom field involves carrying over its name, description, searcher and contexts. For each context the context name, description, issue types, projects, default value, and options -if any, for example for the Select List/Radio Buttons are so on. Also, for the cPrime provided custom fields, the special configurations are exported/imported by KIWI™.
Generates .cfmap files
A successful import generates two mapping files: the current and the next mapping file in the JIRA_HOME_FOLDER/kepler/kiwifolder.
...
For extra functionality of custom field mapping file take a look at Custom Fields Mapping.
Generates a SIL™ aliases file (for Power Scripts™ for Jira users)
If you are using our Power Scripts™ for Jira app (the SIL™ provider) you may have noticed that there is a sil.aliases file in the Kepler folder of your Jira Home folder. This file maps the custom fields to more easy readable names that can be used in the SIL™ scripts. The export embodies the entire file form the source server, including the comment lines.
...
| Note |
|---|
Important notices
|