Issue Summary

The JIM → JWI auto-conversion fails to handle Jira Legacy macros that contain custom fields in the columns parameter but lack the columnIds parameter. Two distinct failure modes occur depending on whether default system fields are present.

Environment
Confluence Cloud — post JIM → JWI auto-conversion (April 2026 rollout)

Precondition
The Jira Legacy macro uses only the columns parameter to reference custom fields (for instance "Space key" field) and does not contain a columnIds parameter. This is common in macros originating from older Confluence Server versions that predate the columnIds parameter (introduced in ~7.x).

Example storage format:

<ac:structured-macro ac:name="jira" ac:schema-version="1" ac:macro-id="734df660-2437-4ac7-93f6-6b7b6b51fed9">
  <ac:parameter ac:name="server">System JIRA</ac:parameter>
  <ac:parameter ac:name="columns">Space key</ac:parameter>
  <ac:parameter ac:name="maximumIssues">20</ac:parameter>
  <ac:parameter ac:name="jqlQuery">key=DOC-745</ac:parameter>
  <ac:parameter ac:name="serverId">b94caeec-8e6d-364f-8e30-9d1dce5682df</ac:parameter>
</ac:structured-macro>

Steps to Reproduce

Scenario 1 — Only custom fields, no default columns
1. Have a Jira Legacy macro where columns contains only custom field references (no system fields like key, summary, type, etc.)
2. The macro does not have a columnIds parameter
3. Auto-conversion runs (JIM → JWI)

 
Scenario 2 — Mix of default columns and custom fields
1. Have a Jira Legacy macro where columns contains default system fields (e.g., key,summary) and custom field references
2. The macro does not have a columnIds parameter
3. Auto-conversion runs (JIM → JWI)

Expected Results

Scenario 1 — Only custom fields, no default columns
The converted JWI macro renders with the custom field columns displayed.

Scenario 2 — Mix of default columns and custom fields
The converted JWI macro renders with both system fields and custom field columns displayed.

Actual Results

Scenario 1 — Only custom fields, no default columns
The converted JWI macro spins indefinitely (loading state never resolves).

Scenario 2 — Mix of default columns and custom fields
The converted JWI macro renders but only displays the default system fields. Custom field columns are silently dropped — they are not selected in the JWI column configuration.

Workaround

Manually recreate the macro selecting all required columns