Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-28783

JIRA Issues Macro shows empty column data if column names have spaces between them

XMLWordPrintable

      If I have a space between column names in the JIRA Issues macro, data is only shown in the first column. The other columns have headings but no data.

      These are OK:
      key;summary;labels;description;acceptance criteria
      key,summary,labels,description,acceptance criteria

      These only show data in the Key column:
      key; summary; labels; description; acceptance criteria
      key, summary, labels, description, acceptance criteria

      Suggested solution: Spaces should be allowed.

      The documentation also needs to be fixed as it is inconsistent between the text in the Macro edit box and the online documentation.

      Relates to CONF-27354 and CONF-28632

      Steps to Reproduce

      1. Link Confluence and JIRA
      2. Create a page with a JIRA Issues Macro
      3. In the macro, enter 'key; description' under Columns - ensuring there is a space between the two
        • You will see that only the Key is displayed
      4. Swap the order of the columns - 'description; key', again ensuring there is a space
        • You will see that the description is now displayed and the key is not.
      5. Now enter 'description;key' or 'key;description' with NO space
        • You will see that all columns display correctly.

            [CONFSERVER-28783] JIRA Issues Macro shows empty column data if column names have spaces between them

            TruongA added a comment -

            The issues is fixed in plugin version 5.0.3 which will be bundled with confluence v 5.2.4. It was ready on On Demand.

            TruongA added a comment - The issues is fixed in plugin version 5.0.3 which will be bundled with confluence v 5.2.4. It was ready on On Demand.

            Carolyn Teo added a comment - - edited

            Based on documentation here: https://confluence.atlassian.com/display/JIRA/Displaying+Search+Results+in+XML
            it says we can use customfield_****. Tried. Didn't work. Neither does allcustom or comment/s
            agree with the above.
            In trial and error, you might wanna verify this if I am right:

            I used the XML and specify the fields, custom field (with spaces in field names)

            http://myjira.com/sr/jira.issueviews:searchrequest-xml/1345SearchRequest-12345.xml?tempMax=1000&field=key&field=summary&field=fixVersions&field=status&field=customfield_10150

            In the jira macro, for the columns I just specify:
            key,summary,fixversion,status,additional description

            Finally it was able to display! Why can't the documentation just say so. I spent 2 days on this!

            Carolyn Teo added a comment - - edited Based on documentation here: https://confluence.atlassian.com/display/JIRA/Displaying+Search+Results+in+XML it says we can use customfield_****. Tried. Didn't work. Neither does allcustom or comment/s agree with the above. In trial and error, you might wanna verify this if I am right: I used the XML and specify the fields, custom field (with spaces in field names) http://myjira.com/sr/jira.issueviews:searchrequest-xml/1345SearchRequest-12345.xml?tempMax=1000&field=key&field=summary&field=fixVersions&field=status&field=customfield_10150 In the jira macro, for the columns I just specify: key,summary,fixversion,status,additional description Finally it was able to display! Why can't the documentation just say so. I spent 2 days on this!

            david greenfield added a comment -

            I Agree 100% with Gerald and Steven. Why do I need to search for an answer on this? It's an easy win.

            It would also be cool, since the query returns columns, to provide a mechanism to simply select which columns to include and not even need to type them by hand (perfectly spelled and with no spaces).

            david greenfield added a comment - I Agree 100% with Gerald and Steven. Why do I need to search for an answer on this? It's an easy win. It would also be cool, since the query returns columns, to provide a mechanism to simply select which columns to include and not even need to type them by hand (perfectly spelled and with no spaces).

            Steven T. Snyder added a comment -

            Fixing the documentation for this would be nice. I wasted some time on this..

            Steven T. Snyder added a comment - Fixing the documentation for this would be nice. I wasted some time on this..

            Gerald Russell added a comment -

            This bug had me frustrated longer than it should have. If Atlassian does not choose to fix it, they should at least update their documentation to note that spaces between column names are not allowed.

            Gerald Russell added a comment - This bug had me frustrated longer than it should have. If Atlassian does not choose to fix it, they should at least update their documentation to note that spaces between column names are not allowed.

              Unassigned Unassigned
              4eb168cf498f Ned Mules
              Affected customers:
              7 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: