KIWI offers you the possibility to move complex workflows from a Jira system to another just with the click of your mouse.
In order to do a To complete import, your the first (and mandatory) step is to export a workflow.
This can be done from the Export page that is accessible from the main KIWI page, which can be found in the Administration view, Add-ons-> KIWI.
Here you will find a combo-box from which you can select the workflow you want to export:
- Go to Jira Administration > Add-ons > KIWI
- Go to Export page
3. Select the workflow you want to export from a combo-box. The page informs, you are about to export a Jira Workflow with all its dependencies (associated statuses, issue types, custom fields and screens).
| Info | ||
|---|---|---|
| ||
The workflow "The default Jira workflow" can not be exported because this is a read only workflow. |
As the description on the page informs, you are about to export a Jira Workflow with all its dependencies (associated statuses, issue types, custom fields and screens).
You can add to your exported workflow a list of pre-import and post-import sil files that will be executed on the Import Jira instance, before (the pre-import files) or after (the post-import files) executing the main import. You definitely know about sil script files if you are using our Power Scripts for Jira app. SIL, or Simple Issue Language is very easy to learn yet powerful and extensible: it's a Java-like language independent of the with no dependence on Jira version, offering power through simplicity and flexibility.
In order to To add a pre-import file, press :
- Click the Add Pre-Import File button
...
- Pop-up dialog
...
- will be opened
- Choose a sil file from the kiwi home folder("PATH_TO_JIRA_HOME/kepler/kiwi")
...
...
4. Click Add button from the pop-up
...
5. Script file is above Add Pre-Import File
...
button
6. The script will be added to the exported kiwi file when
...
clicking Export button
...
7. If there there is no sil script file in the Kiwi home folder(PATH_TO_JIRA_HOME/kepler/kiwi), the pop-up will show a 'No script file' error message:
8. Use the Add Post-Import file button and the same procedure for adding a post-import sil file
...
| Note | ||||
|---|---|---|---|---|
| ||||
| NOTE: 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 too. |
...
4. Click Export button
...
5. You'll see a SUCCESS message on the screen. The exported file can be found in the KIWI home folder (this can be found at "PATH_TO_JIRA_HOME/kepler/kiwi"). Here you will find a new zip file named after your exported workflow(the name is a concatenation of the exported workflow name, the current date in the format yyyyMMddHHmm and .kwi) for instance, Workflowfortest_201310071619.kwi.zip is the file obtained by exporting the workflow Workflowfortest at local time 07.10.2013, 16:19.
After this operation Now you have a brand new KIWI file that you should copy to your Jira system where you'll do the import. Now you've just left Sunda.