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

It is not possible to insert a single JIRA issue or a empty JIRA issue search as a table with the new JIRA issues macro

    • 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.

      This feature request is to provide the ability to insert a JIRA table if it's a single JIRA issue or if the search you provided has no results.

            [CONFSERVER-30117] It is not possible to insert a single JIRA issue or a empty JIRA issue search as a table with the new JIRA issues macro

            For the record: This is also resolved in Confluence 5.2.3 when running JIRA Macros 5.1.3.

            Stefan Hett added a comment - For the record: This is also resolved in Confluence 5.2.3 when running JIRA Macros 5.1.3.

            Truong, thanks for the hint. I had to wait a little, until 5.3 was available on our system. Now it works as desired. Thanks!

            Meino von Spreckelsen added a comment - Truong, thanks for the hint. I had to wait a little, until 5.3 was available on our system. Now it works as desired. Thanks!

            Truong, based on your feedback, I was able to insert a single JIRA issue in table format. It's a combination of both of your points, actually, and it's PERFECT!!

            • If you paste the URL for an issue or enter JQL such as "key = <issue key," you only have one option to display as a single issue, BUT
            • If you enter JQL such has "project = <project> AND key = <issuey key," then you have the option to display even a single issue as a table

            Geoffrey Rodgers added a comment - Truong, based on your feedback, I was able to insert a single JIRA issue in table format. It's a combination of both of your points, actually, and it's PERFECT!! If you paste the URL for an issue or enter JQL such as "key = <issue key," you only have one option to display as a single issue, BUT If you enter JQL such has "project = <project> AND key = <issuey key," then you have the option to display even a single issue as a table

            TruongA added a comment -

            meino: This issue is already fixed as your expectation. If only 1 issue or no issues of JQL returns, you can choose options to display as table or count. Could you check again your case with the fix version of plugin?

            TruongA added a comment - meino : This issue is already fixed as your expectation. If only 1 issue or no issues of JQL returns, you can choose options to display as table or count. Could you check again your case with the fix version of plugin?

            Remark on your second point: You use a certain JQL-Query (to select certain issues) with certain display columns (to display CERTAIN ASPECTS of the issues) on a confluence page. You design your text and layout around the table so that this makes sense. So, if temporarily the JQL-Query returns only 1 issue you cannot display want you want. I consider this not accepable. Also, I often have the case, where I create a confluence page with tables, that are empty at creation time (e.g. a table with sprint results at the beginning of the sprint). However, I want to configure the table and columns at that time. Then (during the sprint) the table gets filled when the developers resolve their issues.
            I think it is indispensable, that you can configure the table independent of the no. of issues the JQL returns at the time!

            Meino von Spreckelsen added a comment - Remark on your second point: You use a certain JQL-Query (to select certain issues) with certain display columns (to display CERTAIN ASPECTS of the issues) on a confluence page. You design your text and layout around the table so that this makes sense. So, if temporarily the JQL-Query returns only 1 issue you cannot display want you want. I consider this not accepable. Also, I often have the case, where I create a confluence page with tables, that are empty at creation time (e.g. a table with sprint results at the beginning of the sprint). However, I want to configure the table and columns at that time. Then (during the sprint) the table gets filled when the developers resolve their issues. I think it is indispensable, that you can configure the table independent of the no. of issues the JQL returns at the time!

            TruongA added a comment - - edited

            georodgers: There are two cases here depend of JQuery you insert:

            • If you type an issue key or JQuery as "key = <issue key>", you only have one option to display as single issue. Please share me why you want to show this case as table.
            • If you type a JQL (i.e "status = open") and only 1 issues return, you will have options to display as single, count or table.

            TruongA added a comment - - edited georodgers : There are two cases here depend of JQuery you insert: If you type an issue key or JQuery as "key = <issue key>", you only have one option to display as single issue. Please share me why you want to show this case as table. If you type a JQL (i.e "status = open") and only 1 issues return, you will have options to display as single, count or table.

            This has a Fix Version of 5.3, but I don't see in the OnDemand instance how it is possible to keep a single JIRA issue in table format. Has this issue not been rolled out to OnDemand yet, or am I just missing something? Thanks!

            Geoffrey Rodgers added a comment - This has a Fix Version of 5.3, but I don't see in the OnDemand instance how it is possible to keep a single JIRA issue in table format. Has this issue not been rolled out to OnDemand yet, or am I just missing something? Thanks!

            Piotr Gutaker added a comment - - edited

            Hello,

            Any update on this issue? It is relatively serious bug as it breaks the layout of a table, please see the screenshots. Once the filter returns no issues any more, the table breaks as shows in view_mode_JIRAmacro.PNG.

            Piotr Gutaker added a comment - - edited Hello, Any update on this issue? It is relatively serious bug as it breaks the layout of a table, please see the screenshots. Once the filter returns no issues any more, the table breaks as shows in view_mode_JIRAmacro.PNG.

              Unassigned Unassigned
              smansour Sherif Mansour
              Votes:
              14 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: