---
title: "Integration with Configuration Manager for Jira"
canonical: "https://support.appfire.com/space/CW/69307062/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. Update on Transition for Jira integrated with Configuration Manager making it easy to move data between instances. This integration enables administrators to bundle the following Update on Transition 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">Global app configuration data</span>
- <span style="color: #000000">Workflow post function configurations</span>
- <span style="color: #000000">Validator configurations</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 Update on Transition workflow data, you must disable the uot-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 Update on Transition for Jira installed before migrating data.</span>

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

<span style="color: #000000">Update on Transition workflow configurations are migrated with the limitations mentioned in this section.</span>

- <span style="color: #000000">Issue fields listed here (that contain issue keys) are copied as-is into the target instance while migrating the workflow post function. </span><span style="color: #000000">*Update Issue*</span><span style="color: #000000"> processes 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">Issues to update</span>
- <span style="color: #000000">When the </span><span style="color: #000000">*Condition 1 or Condition 2 *</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">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>
- [App integrations with Configuration Manager](https://appfire.atlassian.net/wiki/x/EIcHEg)