Issue Summary

A column disappears unexpectedly in the Jira issue macro on Confluence pages, despite being visible in the Jira Issue Navigator.

This happens when the JQL results return an issue that does not have the field due to the context or field schema used.

Steps to Reproduce

Jira Setup:

• Navigate to the Jira Issue Navigator.
• Execute the following JQL:

  project=xxxx and issuetype=sub-task

  .

• Ensure the columns "Issue Type," "Summary," and "Resolved" are displayed.

Confluence Setup:

• Create or edit a Confluence page.
• Insert the Jira work items (previously called Jira issue) macro with the same JQL.
• Publish the page and confirm that both the Issue Navigator and macro display the same columns and results.

Add Custom Field:

• In Jira, create a new custom field (for instance, a Date Picker) and add it to the project's screens.
• Populate this field with values across different issue types, including sub-tasks. 
• In the Issue Navigator, add the new Date Picker column.

Update Confluence Page:

• On the Confluence page, edit the Jira issue macro to include the new Date Picker column, and then publish the page.
• Confirm that both the Issue Navigator and the macro display the same results, now including the Date Picker column.

Change Field Context:

• In Jira, change the context of the new Date Picker field. Select only the issue types "Epic, Story, Bug and Task".  Do not include sub-tasks.
• Verify that the Issue Navigator still lists the issues with the Date Picker column.

Refresh Confluence Page:

• Refresh the Confluence page and edit the Jira issue macro.
• Perform a search using the same JQL.

Expected Results

The Confluence page should display the same results as the Jira Issue Navigator, including the Date Picker column.

Actual Results

• The Date Picker column disappears from the Confluence page (✗).
• When accessing the Columns menu, the column temporarily reappears (✓).
• After performing a search or refreshing the page, the column disappears again (✗).

Impact

This issue affects the consistency and reliability of data presentation between Jira and Confluence, disrupting users who rely on the Confluence page for comprehensive issue tracking.

Workaround

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

Note:
If the sub-task is added back to the context, the custom field will become visible on the screens, which may be undesirable for the customer.