KIWI KIWI exports/imports the custom fields from the screens related to the workflow (e.g. transition screens and the screens that are found in the related Issue type screen schemes).
...
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
...
- 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 scripts, all that is needed to fully restore the configurations
...
- . For dynamic queries, the custom field ids are updated with their corresponding 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. |
- For SIL User Picker and SIL Script Custom Field, the SIL Script for each context is carried over.
- For REGEX custom field the Regex configuration is exported/imported.
- For the Power Custom FIelds PRO custom fields, all the configuration is carried (the data source, the option type, the filtering strategy, etc)