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

Confusing instructions about the 'Columns' field in JIRA Issues Macro

XMLWordPrintable

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      After embedding a JQL Query in Confluence using the 'JIRA Issues' Macro the instructions on how to place the columns you want to display are confusing.

      For instance, if you want to display the key, summary and type columns, looking at the instructions underneath the field, you will end up placing something like this:

      key, summary, type

      However, if you do that, you'll only get the key as a result. The problem lies in the fact that there should be no spaces between the selected fields. Actually, you should place this:

      key,summary,type

      Would be nice to have an (e.g. key,summary,etc) within the instructions.

            [CONFSERVER-28632] Confusing instructions about the 'Columns' field in JIRA Issues Macro

            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 already 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 already on On Demand.

            Sherif Mansour added a comment -

            This is fixed with the new autocomplete picker we have for the JIRA issues macro.

            Sherif Mansour added a comment - This is fixed with the new autocomplete picker we have for the JIRA issues macro.

              tvu TruongA
              brosa Bruno Rosa
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: