#### Problem
After transferring a project using Configuration Manager for Jira (CMJ), users have observed that epic names appear unlabelled, disrupting project tracking and management.
#### Symptoms
Epic names display correctly in the source Jira instance but appear unlabelled in the target instance after migration.
...
The problem persists even after multiple migrations.
#### Root Cause Analysis
The root cause was identified through detailed logs and user reports:
...
The discrepancy in field names between source and target instances leads to unlabelled epic names post-migration.
#### Resolution
To resolve the issue, the following steps are recommended:
**Verify Jira and CMJ Versions**
Ensure that both source and target Jira instances have the same versions.Source Jira Version: 9.4.14
Target Jira Version: 9.4.14
CMJ Version: 6.15.3
a
a
a
a
a
a
a
a
a
a
a
a
**Collect Support Logs**
Navigate to the "Logging and Profiling" section in Jira Administration, configure `com.botronsoft` to DEBUG level, and perform the project migration to collect relevant logs.
...
[Configuration Manager for Jira - Appfire Documentation](https://appfire.atlassian.net/wiki/spaces/CMJ/overview )
[Configuration Manager for Jira - Botron Software](Configuration Manager for Jira - Botron Software )
...