Issue Summary

Running a Migration from DC to Cloud using JCMA resulted in failure of multiple project failing at the JiraImport step.

• We found the below errors in the Import logs. Checking on the errors on "IG" project migration as an example, I can see these:

  2025-02-07T18:59:55 ERROR IG project-import Jira failed to ingest entity Issue Type 'wiczenie'. Reason: RuntimeException: issue type dual write into jira and arj config failed. This caused 2 other item(s) to fail
  
  2025-02-07T18:59:58 ERROR IG project-import We couldn't import Issue Type Scheme 'Default Issue Type Scheme'. Reason: RuntimeException: issue type dual write into jira and arj config failed. This caused 1 other item(s) to fail
  

  2025-02-07T19:00:37 ERROR IG project-import Jira failed to ingest entity Issue IG-1. Reason: project: Specify a valid project ID or key. This caused 0 other item(s) to fail
  2025-02-07T19:00:37 ERROR IG project-import Jira failed to ingest entity Issue IG-2. Reason: project: Specify a valid project ID or key. This caused 0 other item(s) to fail
  2025-02-07T19:00:37 ERROR IG project-import Jira failed to ingest entity Issue IG-3. Reason: project: Specify a valid project ID or key. This caused 0 other item(s) to fail
  2025-02-07T19:00:37 ERROR IG project-import Jira failed to ingest entity Issue IG-4. Reason: project: Specify a valid project ID or key. This caused 0 other item(s) to fail
  2025-02-07T19:00:37 ERROR IG project-import Jira failed to ingest entity Issue IG-5. Reason: project: Specify a valid project ID or key. This caused 0 other item(s) to fail
  2025-02-07T19:00:37 ERROR IG project-import Jira failed to ingest entity Issue IG-6. Reason: project: Specify a valid project ID or key. This caused 0 other item(s) to fail

• The Export Logs were seen to have the below errors. 
  Export file

  Unable to find source-code formatter for language: code panel. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, javascript, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml

  { "_id": "mri:mig:jira/classic:issueType:11600", "name": "w\u0000i\u0000c\u0000z\u0000e\u0000n\u0000i\u0000e", "description": "", "subtask": false, "avatar": null, "managedIssueTypeKey": null, "hierarchyLevel": "mri:mig:jira/classic:issueTypeHierarchy:0", "projectConfiguration": null, "scope": null }
  

As the explanation provided, IssueType's name was having escape sequence, similar to null (For Eg: Ćwiczenie or wiczenie, which we can not be imported. This should be solved at the Export level for the Import to work properly.

Expected Results

• Migration completes successfully for the project via JCMA

Actual Results

• Migration fails at the "JiraImport" step. The progress percentage is very low at 10% to 23%.

Workaround

• Customer's can either change the "Issue Type Scheme" for the failed projects.
• Migrate from DC to Cloud

OR

• Remove the problematic Issue Type from the Issue Type Scheme.
• Migrate from DC to Cloud

OR

• Create a new issue type without any special characters.
• Bulk Move all the Issues from problematic Issue type to the new Issue Type.
• Remove the problematic Issue Type from the Issue Type Scheme which has no issues associated to it.
• Migrate from DC to Cloud.