Versions Compared

Old Version 12

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.

...

  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 is 9.4.14, the Target Jira version should also be 9.4.14. Both instances should be using the same version of CMJ.”

  2. Collect Support Logs
    Navigate to the "Logging and Profiling" section in Jira Administration, click Configure, add . Click Configure. Add com.botronsoft, and set the log level of the com.botronsoft to 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 | ​ 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
    Copy the epic name values in the target instance into the appropriate field(e.g., 에픽의 이름) to update them.

  6. Replicate and Analyze
    Set up a test environment to test out the behavior. You can refer to this page, Jira Clones, for information on how to do that.

...