Issue Summary

When using Jira Cloud automation to clone issues, rich text fields that contain  multibyte characters(like Japanese) are corrupted in the cloned issue.

This problem only occurs when cloning via Automation for Jira.
Cloning the same issue via the Jira UI (More → Clone) preserves the formatting as expected.

Steps to Reproduce

1. In a Jira project, configure (or identify) an issue type that has at least one rich text field:
   1. e.g. Description or a rich text custom field.
2. Create a new issue, and enter content in the rich text field such as:
   1. Multibyte characters with text styles and non-text styles.
   2. Example: テストですテストですテストですテストですテストです_テストです^テストです
3. Save the issue.
4. Create an automation rule:
   1. Trigger: For example, Issue created or Manual trigger.
   2. Action: Clone issue.
5. Set the rule so that the rich text field(s) are included in the cloned issue
   (use the default clone behaviour; no additional field edits).
6. Execute the automation rule so that it clones the issue.
7. Open the cloned issue and check the rich text field(s).

Expected Results

• The cloned issue’s rich text field(s) are identical to the original
• Cloning via Automation behaves the same as cloning via the standard Jira UI “Clone” function.

Actual Results

In the cloned issue (created by the automation rule), the rich text field content is corrupted. 

Workaround

Cloning issue manually via Jira UI