-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Action - Clone Issue, Action - Issue Actions
Currently, when using Jira Automation to set the Description field, formatting such as backtick inline code is not rendered the same way as when editing directly in Jira. Automation interprets the content differently, leading to inconsistent appearance and extra manual work to fix formatting.
Expected Results :
Descriptions updated by automation should display inline code (backticks) as they appear when added manually through the Jira editor.
Actual Results :
Descriptions updated by automation show backtick code as plain text causing formatting mismatches compared to manual editing.
Workaround :
If the template is already available in another work item, you can copy the Description directly from that item using automation:
Steps:
- Use a manual or any trigger.
- Add a "Lookup issues" action with JQL to fetch the work item containing the template (e.g., key = TEST-123).
- In the "Create issue," "Clone issue," or "Edit issue" action, set the Description field using the smart value below. This will copy the Description from TEST-123 and add it to the target issue, preserving the formatting.
Example Smart Value:
{{lookupIssues.description}}
- is related to
-
JRACLOUD-98222 Cloning an issue does not render markdown/rich text in the Description field — content displays as plain text with raw markdown characters
-
- Needs Triage
-