KIWI KIWI™ exports/imports the custom fields from the screens related to the workflow (e. g. For example transition screens and the screens that are found in the related Issue type screen schemes).
All Jira standard custom fields are supported. These custom fields are exported along with their contexts: The issue types, projects, default value and options(if the custom field may have options) associated related to each context are exported and imported on the deployment machine.
Beside these, KIWI KIWI™ knows how to handle the following cPrime provided Custom Fields:
For these custom fields , the special configurations (if there are any) are carried over, so no change is needed on the deployment machine. For instance:
- For Power Actions Custom Field Field™ all the Actions(buttons) together with their scripts are exported and restored on the import server.
- For Database Custom Field the configurations from the cPrime parameters page are carried over: the JNDI names, Sql queries, SIL SIL™ scripts, all . Everything that is needed necessary to fully restore the configurations. For dynamic queries, the custom field ids IDs are updated with their corresponding ids IDs from the target Jira instance.
| Info |
|---|
For DBCF fields the used data sources must be manually configured on the Import server. Please see Data Source Configuration for details on how to manually configure a Data Source manually. |
- For SIL SIL™ User Picker and SIL SIL™ Script Custom Field , the SIL SIL™ Script for each context is carried over.
- For REGEX custom Regex Custom field the Regex configuration is exported/imported.
- For the Power Custom FIelds PRO custom fields, all the Fields PRO full configuration is carried (transferred: the data source, the option type, the filtering strategy , etc)and so on.