Problem Definition

When we add a JIRA Issue Macro in a Confluence page, Confluence displays default columns from JIRA irrespective of the columns that were selected in JIRA when viewing the JQL.

Suggested Solution

Suppose if we filter issues in JIRA and select the desired columns to be displayed using the Columns button. When the JIRA filter URL is used in the Confluence page using JIRA Issue Macro, it includes the selected columns.

Why this is important

This will provide a more robust way when sharing JQL and simplify inserting JQL tables into a Confluence page.

Workaround

Install the Confluence Source Editor, which allows quick editing of the XML that generates the macro.

Editing the <ac:parameter ac:name="columns"> line directly can be quicker than the current user interface.

 <ac:structured-macro ac:macro-id="9ed09b85-ef84-4ec8-9a34-b3f39ab0e11b" ac:name="jira" ac:schema-version="1">
    <ac:parameter ac:name="server">Your Company JIRA</ac:parameter>
    <ac:parameter ac:name="columns">key,summary,type</ac:parameter>
    <ac:parameter ac:name="maximumIssues">20</ac:parameter>
    <ac:parameter ac:name="jqlQuery">assignee = currentUser() AND resolution = Unresolved order by updated DESC </ac:parameter>
    <ac:parameter ac:name="serverId">02898d7b-114e-357c-9c67-1a61b19662a7</ac:parameter>
  </ac:structured-macro>