Issue Summary

If description in a Jira issue is formatted with markdown, the during migration the following error is seen in Cloud logs:

Fabric Services Prestore error(s):{"errors":{"0":["ADF validation error: incoming adf does not comply with Atlassian Document Format"]}}

This is reproducible on Data Center: (yes)

Steps to Reproduce

1. Create an Issue on Jira Server
2. Use markdown formatting for the description field
3. Migrate the project/issue to Cloud

Expected Results

The issue is migrated to the cloud successfully

Actual Results

The below exception is thrown in the Splunk logs:

Fabric Services Prestore error(s):{"errors":{"0":["ADF validation error: incoming adf does not comply with Atlassian Document Format"]}}

On Server/Migration logs, the following error is seen:

2022-07-12 07:26:56.672072 ERROR MYPROJ project-import We couldn't import Issue MYPROJ-2. Reason: TransactionRuntimeException: org.ofbiz.core.entity.GenericTransactionException: Commit failed, rollback previously requested by nested transaction.. This caused 1 other items to fail.

Workaround

There is no workaround as such. A customer, with 15 such failed issues, was advised the following:

• save the description contents to a file
• Use the file link in the description
• Migrate
• Use the file link on the cloud to paste the description back into the issue

However, this workaround does not scale.