Issue Summary

• Jira Work Item macros nested under the legacy panel macro returns custom fields returns raw JSON values.
  • Related to the issue here CONFCLOUD-83592 for Word export.

Steps to Reproduce

• In Jira
  1. Create a Rich text custom field in Jira and assign in to a Jira screen in any project.
  2. Add any text into this field for an issue.
• In Confluence
  1. Create a page in the Legacy Editor
  2. Insert a panel macro with some simple formatting
     • Example: Dotted border
     • This step is needed to get the panel post conversion.
  3. In the panel, add in the Legacy Jira issue macro
     • Pointing to the issue with the Rich text custom field in Jira.
  4. Publish the page, and convert to the new editor.
  5. The new editor will still be using the legacy Jira issue macro
     • Rich text fields load fine during page edit and view
  6. Remove the Jira issue macro, and swap it with the Jira Work Items macro
  7. Rich text fields load fine during page edit
  8. And once published, we get the JSON strings

     • {"type":"doc","version":1,"content":[{"type":"paragraph","content":[{"type":"text","text":"Plain text"}]}]}

Expected Results

• The values in the custom fields should only be returning the values, as they appear in the Page Edit screen.

Actual Results

• The values in the custom fields appear as the raw JSON response when on the Page View screen.

Workaround

• Currently there is no known workaround for this behavior. A workaround will be added here when available