Issue Summary

The Jira Work Item (JWI) macro hangs indefinitely in an animated loading skeleton / spinning state when configured to display a column corresponding to a Jira field that no longer exists, was renamed, or is unavailable to the viewer.

Although the backend network request resolves successfully, the macro fails to handle the payload containing unresolved display columns and never exits the loading state.

Steps to Reproduce

1. In Confluence, insert a Jira Work Item macro on a page.
2. Configure the macro with a JQL query and select specific custom fields to display as table columns.
3. Publish the page and verify the macro renders data as expected.
4. In Jira (Settings > Issues > Custom Fields), delete or rename one of the custom fields selected in step 2 (or restrict field permissions for the viewing user).
5. Return to the Confluence page and hard refresh / reload.

Expected Results

The macro should gracefully handle missing or unresolved fields by either:

• Rendering the table with the remaining valid columns (optionally displaying an inline notice or a blank header for the missing field), OR
• Displaying a clear, user-friendly error/warning message explaining that one or more selected columns are invalid or inaccessible.

Actual Results

The macro gets stuck in an infinite loading state, continuously showing the animated skeleton / spinner without rendering any data or displaying an error message.

Workaround

To resolve the macro loading issue:

1. Edit the affected Confluence page and select the *Jira Work Item* macro.
2. Open the macro settings panel / edit dialog.
3. Remove the deleted/invalid field from the selected columns and re-save/re-publish the page.

Tip for identifying the missing field:
Run the same JQL query directly in the Jira Issue Navigator (Filters > View all issues) and add the columns one by one to determine which field is missing or returning an error.