Page Comparison

...

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.”
Collect Support Logs
Navigate to the "Logging and Profiling" section in Jira Administration, 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
Review Audit Logs
To obtain detailed audit logs, follow instructions from [audit log|https://appfire.atlassian.net/wiki/spaces/CMJ/pages/198246829/Audit+Logging?search_id=3abce5d5-920f-4de5-ba6c-79d3e0110fdc ]
[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 ).

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

Code Block

language	sql

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'

);

Manual Field Updates
Copy the epic name values in the target instance into the appropriate field(e.g., 에픽의 이름) to update them.
Replicate and Analyze
Set up a test environment to test out the behavior. You refer to this page, Jira Clones, for information on how to do that.

...

Versions Compared

Old Version 13

New Version 14

Key