---
title: "Integration with Configuration Manager for Jira"
canonical: "https://support.appfire.com/space/CSOT/68750796/Integration%20with%20Configuration%20Manager%20for%20Jira"
format: markdown
---
> Macro (aura-html)

# <span style="color: #000000">Overview</span>

<span style="color: #000000">[Configuration Manager for Jira](https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira?hosting=server&tab=overview)</span><span style="color: #000000"> is a powerful app that allows Jira administrators to transfer configuration data between different Jira Server and DC instances. Create on Transition for Jira </span><span style="color: #000000">is</span><span style="color: #000000"> integrated with Configuration Manager making it easy to move data between instances. This integration enables administrators to bundle the </span><span style="color: #172b4d">global app </span><span style="color: #000000">configurations</span><span style="color: #172b4d"> and workflow post function </span><span style="color: #000000">configurations with Configuration manager snapshots in the source instance and restore </span><span style="color: #000000">these snapshots </span><span style="color: #000000">while importing them into</span><span style="color: #000000"> the target instance.</span>

> ⚠️ - <span style="color: #000000">Currently, note that the </span><span style="color: #000000">*Merge Configuration *</span><span style="color: #000000">deployment mode (on the first page of configuration wizard) is not supported </span><span style="color: #000000">while deploying</span><span style="color: #000000"> the configuration snapshot for global app configuration data.</span>
> ⚠️ - <span style="color: #000000">It is recommended to verify and test the app configuration data migration in a staging environment before deploying it in production.</span>
> ⚠️ - <span style="color: #000000">If you do not intend to migrate Create on Transition workflow data, you must disable the cot-workflow-participant-handler module in the </span><span style="color: #000000">*Manage apps *</span><span style="color: #000000">page.</span>

# <span style="color: #000000">Pre-requisites</span>

<span style="color: #000000">Ensure both the source and target instances have the same version of Configuration Manager for Jira and Create on Transition for Jira installed </span><span style="color: #000000">before</span><span style="color: #000000"> migrating data.</span>

# <span style="color: #000000">Limitations</span>

<span style="color: #000000">Issue fields listed here (that contain issue keys) are copied as-is into the target instance while migrating workflow</span>* *<span style="color: #000000">post functions. </span><span style="color: #000000">*Create Issue *</span><span style="color: #000000">and </span><span style="color: #000000">*Create Sub-task *</span><span style="color: #000000">process them once Configuration Manager imports the referenced issues into the target instance. When the referenced issues are imported into a new project, the administrator must update the respective issue keys.</span>

- <span style="color: #000000">Create link</span>
- <span style="color: #000000">Copy links</span>
- <span style="color: #000000">Copy remote links</span>
- <span style="color: #000000">Copy attachments</span>
- <span style="color: #000000">Entry parent</span>

<span style="color: #000000">When the following</span><span style="color: #000000">* *</span><span style="color: #000000">fields have values containing custom field names or IDs, they are not processed and are copied as-is to the target instance.</span>

- <span style="color: #000000">Conditions</span>
- <span style="color: #000000">Create multiple issues</span>

<span style="color: #000000">It is recommended that the administrator creates the following field entities if they have not been migrated by Configuration Manager:</span>

- <span style="color: #000000">Components</span>
- <span style="color: #000000">Fix versions</span>
- <span style="color: #000000">Affected versions</span>
- <span style="color: #000000">Labels</span>
- <span style="color: #000000">Reporter</span>
- <span style="color: #000000">Assignee</span>
- <span style="color: #000000">Watchers</span>

## <span style="color: #000000">Substitution variables processing</span>

### <span style="color: #000000">Custom fields</span>

- <span style="color: #000000">When substitution variables are used to set custom fields in the source instance, the following representations are not currently supported in workflow post function migrations:</span>
- <span style="color: #000000">entry_customfield_</span><span style="color: #000000">*<issue key>*</span>
- <span style="color: #000000">values_customfield_</span><span style="color: #000000">*<custom field id>*</span>
- <span style="color: #000000">values_customfield_</span><span style="color: #000000">*<issue key>*</span><span style="color: #000000">(entry)</span>
- <span style="color: #000000">transition_customfield_</span><span style="color: #000000">*<custom field id>*</span>

### <span style="color: #000000">Others</span>

<span style="color: #000000">When the following fields are defined using substitution variables in the source instance, they are not processed and are copied as-is to the target instance:</span>

- <span style="color: #000000">JQL query</span>
- <span style="color: #000000">Acting user</span>

### <span style="color: #000000">Additional links</span>

- <span style="color: #000000">[Configuration Manager for Jira](https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira?hosting=server&tab=overview)</span>
- <span style="color: #000000">[App integrations with Configuration Manager](https://appfire.atlassian.net/wiki/x/EIcHEg)</span>