KIWI™ tools

Contents

Besides its main purpose of carrying over a workflow and its dependencies, KIWI™ also produces different deltas: CF mapping files and sil.aliases files and offers the tools to merge these files.

CF Mapping files

The cf mapping files: the current and the next mapping file offer you the custom field mappings that can be reused. They are generated by a successful import in the JIRA_HOME_FOLDER/kepler/kiwi folder. The next mapping file contains all the custom field mappings resulted from the import according to your used .cfmap file and according to your screen selection, including the created custom fields. This can be used for a future import on the same server.The current mapping file contains all the mappings according to your used .cfmap file and according to your screen selection for the custom fields existing on the Import server. This is different from the next mapping file by not including the newly created custom fields. This file is useful for executing the same import on another server that is identical as a structure to the Jira Import server where the file was generated. To merge two generated CF Maps files, you need to use the .cfmap merging tool.

SIL aliases files

The sil.aliases file is related to SIL™, Simple Issue Language™ and our Power Scripts™ for Jira app. This file, located in the Kepler home folder, maps the custom fields into a more easy readable names that can be used in the SIL™ scripts.A successful import generates a kiwi local sil.aliases file, different from the sil.aliases file described above, in the Kiwi™ home folder. This file contains only those custom field aliases that were imported, re-mapped according to your .cfmap file and according to your screen selection. To merge your generated file in the sil.aliases you need to launch the sil.aliases merging tool.