Versions Compared

Old Version 11

changes.mady.by.user Sudhir Kv

Saved on

compared with

New Version Current

changes.mady.by.user Sudhir Kv

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

(blue star) Problem

After transferring a project using Configuration Manager for Jira (CMJ), users have observed that epic names appear unlabelled, disrupting project tracking and management.

(blue star) Symptoms

  1. Epic names display correctly in the source Jira instance but appear unlabelled in the target instance after migration.

  2. The issue occurs irrespective regardless of the language of the epic names, affecting both English and Korean labels.

  3. The problem persists even after multiple migrations.

...

  1. Verify Jira and CMJ Versions
    Ensure that both source and target Jira instances have the same versions. For example, if the Source Jira

    Version:

    version is 9.4.14

    , the Target Jira

    Version:

    version should also be 9.4.14

    CMJ Version: 6.15.3

    . Both instances should be using the same version of CMJ.

  2. Collect Support Logs
    Navigate to the "Logging and Profiling" section in Jira Administration, configure . Click Configure. Add com.botronsoft, and set the log level of the com.botronsoft to the DEBUG level, and perform the project migration to collect relevant logs DEBUG. Share the support zip by referring to https://confluence.atlassian.com/support/create-a-support-zip-790796819.html.

  3. Review Audit Logs
    To obtain detailed audit logs, follow instructions from [Configuration Manager for Jira Audit Logging](​Audit Logging | Audit Log Details ​ https://appfire.atlassian.net/wiki/spaces/CMJ/pages/198246829/Audit+Logging?search_id=3abce5d5-920f-4de5-ba6c-79d3e0110fdc).

  4. Execute Database Queries
    Run these SQL queries on both source and target databases to verify epic labels and colors:

    Code Block
    languagesql
    SELECT * FROM customfield;

SELECT * FROM customfieldvalue

WHERE customfield = ANY (

SELECT id FROM customfield

WHERE customfieldtypekey LIKE 'com.pyxis.greenhopper.jira:gh-epic-label'

OR customfieldtypekey LIKE 'com.pyxis.greenhopper.jira:gh-epic-color'

);

  5. Manual Field Updates
    Update Copy the epic name values in the target instance by copying them into the appropriate custom fields field(e.g., 에픽의 이름) to update them.

  6. Replicate and Analyze
    Perform the migration in a controlled environment and analyze the behavior. This includes setting up conditions similar to those in the production environment to replicate the issue accuratelySet up a test environment to test out the behavior. You can refer to this page, Jira Clones, for information on how to do that.

Example screenshots before and after deployment

...

Unlabelled epic names after project transfer via CMJ can be resolved by ensuring consistency in field names between source and target Jira instances. Following the outlined steps, users can maintain accurate epic labels, improving project tracking and management. For any additional assistance, please contact support or submit a ticket.

References