Issue Summary

When using the Jira Work Item (JWI) macro in Confluence Cloud, custom field column headers revert to their internal raw IDs (e.g., Customfield_13100) instead of their friendly display names if the JQL query returns no results.
This affects the page view and exports (Word and third-party apps like Scroll Word Exporter).

Steps to Reproduce

1. Create a Confluence Cloud page and add a Jira Work Item macro in table view.
2. Configure the macro to include a custom field column (e.g., "Release Notes Summary").
3. Set the JQL filter so that it returns at least one result. Observe that the column header displays the friendly name correctly.
4. Update the JQL filter so that it returns 0 results.
5. View the page or export it to Word.

Expected Results

The table header should consistently display the human-readable custom field name regardless of whether the JQL returns results.

Actual Results

When the JQL returns 0 rows, the table header displays the raw backend field ID (e.g., Customfield_13100).
Once an issue matches the JQL again, the friendly name is restored.

Workaround

• Adjust JQL:
  Modify the query to ensure at least one issue is returned to trigger the metadata resolution.
• Native PDF Export:
  Use Confluence's native PDF exporter, which uses a different rendering path and is not affected by this bug.