Issue Summary

Assets DC → Cloud migration: Description (textarea) attributes show raw formatting/markup tags in Cloud editor instead of rendered text.

Steps to Reproduce

1. On Jira DC with Assets, create or identify an object type with a Description (textarea) attribute.

1. For one or more objects, populate the Description with formatted content, e.g.:

• • Multiple paragraphs / line breaks

• • Bulleted text

• • Any content that DC stores with underlying markup/wrapped structure.

1. Run a DC → Cloud migration including Assets (JCMA), with this schema in scope.

1. In Jira Cloud, open the migrated Assets schema and view an affected object.

1. Inspect the Description attribute in the Cloud object editor.

Expected Results

• Description text in Cloud is displayed in a clean, human-readable form, with line breaks/paragraphs rendered appropriately.

• Any underlying DC/ADF/wikitext/HTML representation is parsed and rendered, not shown as raw tags or structural markers.

Actual Results

• In Cloud, the Description attribute shows raw formatting/markup tokens directly in the editor.

• • Examples (patterns seen):

• • • Literal paragraph or line-break tags (e.g. <p>, <br> or equivalents).

• • • Structural markers that look like wiki/ADF or JSON-like fragments (e.g. {{{} {"type":"paragraph", ...}

      {}}}) embedded in the text.

• End users see these tags as plain text instead of formatted content.

Workaround

Workaround 1: Manual edit (small scale)

For a few objects, open each in Cloud Assets editor and remove or retype the description. Quick but not scalable.

---

Workaround 2: Bulk Edit via Assets UI

1. Use an AQL filter in Assets schema to find affected objects, e.g.:
   objectType = "<ObjectTypeName>" AND "Description" is not EMPTY

1. Select objects → Bulk Actions → Edit

1. Choose Description and set or overwrite with plain text.

Limitation: Bulk edit applies the same value to all selected objects, so it only works for blanking or setting a common description, not unique content.

---

Workaround 3: CSV Export → Clean → Re-import (recommended for scale)

This is the best method for customers:

1. Export affected objects as CSV:
   Assets schema → select object type → Bulk Actions → Export Objects (Data consistent format)

1. Clean the CSV— remove all markup tags in Description (e.g. <p>, <br>, {"type":"paragraph",...}) using find-replace, regex, or script, leaving only plain text.

1. Re-import the cleaned CSV:
   Schema Settings → Import tab → Create Import (CSV Import)

• • Map to existing object type

• • Set identifier (e.g. Name or Key) to match existing objects

• • Map only the Description attribute

• • For missing objects: Ignore | For empty values: Ignore

• • Run the import

This keeps all other data intact and only replaces Description with clean text.