Issue Summary

When cloning an issue in a company-managed project, the Description field in the cloned issue loses its rich text formatting. Markdown characters (e.g., **, #, _, backticks) are displayed as plain text instead of being rendered as formatted text. The source issue renders correctly; the clone does not.

This behavior is consistent with JRACLOUD-81555, which covers the same rendering failure during issue creation. However, JRACLOUD-81555 was closed as "Won't Fix" with the expectation that the Default Text Renderer deprecation would resolve it. As of April 2026, the issue persists for the clone operation.

Steps to Reproduce

1. In a company-managed project whose Field Configuration has the Description field set to "Default Text Renderer", open an existing issue with a properly rendered rich text description.

1. Clone the issue using the Clone action in the Jira UI.

1. Open the cloned issue and inspect the Description field.

Expected Results

The cloned issue's Description field should display the same rich text formatting as the source issue.

Actual Results

The cloned issue's Description field displays raw markdown characters as plain text. Formatting such as bold, headings, inline code, and lists are not rendered.

Workaround

Edit the cloned issue's description, delete the content, and re-type or paste it back. This forces re-rendering through the ADF engine.

Alternatively, remove the description before cloning and add it manually after the clone is created.

Additional notes

This issue occurs only in team-managed projects, not in company-managed projects that use the Default Text Renderer.

The renderer setting for the Description field can no longer be changed in the Jira admin UI due to the ongoing deprecation of the Default Text Renderer. It can still be updated to "Wiki Style Renderer" via the The Jira Cloud platform REST API, which may prevent future occurrences but does not fix already-affected issues.