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

Add ability to predefine ordering of JIRA Issues Macro/respect filter order by

XMLWordPrintable

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

      Apparently the JIRA Issues Macro used to have the ability to define sorting and pagination. CONF-29991 addressed this concern, but sorting was never introduced as a parameter that can be defined on the macro itself. Instead, sorting is undefined when the table is loaded and the viewer of the page can sort as they like.

      The initial sorting should be able to be defined so that the document can display issues in the order the document embedding the view is concerned with (e.g. fixVersion, updated, etc.). Interaction with the table should be left in (could be an option to disable even).

      If adding it to the macro parameters is undesirable for some reason, the macro should at least respect the sorting that the filter itself defines. It currently does not, as mentioned here: https://answers.atlassian.com/questions/228129/answers/9871223?flashId=-257275889

      Workaround

      Using the direct JQL instead of a filter allows the JIRA Issues macro to respect the ORDER BY clause of the query.

            [CONFSERVER-35323] Add ability to predefine ordering of JIRA Issues Macro/respect filter order by

            Jackie Drysdale added a comment -

            No sure if worth commenting due to age. 

            Agree that this is a bug, makes the macro useless in presenting things like release dates in order. 

            Jackie Drysdale added a comment - No sure if worth commenting due to age.  Agree that this is a bug, makes the macro useless in presenting things like release dates in order. 

            Kel Hill added a comment -

            This deficiency makes Confluence useless to me for publishing our release notes. I need my release notes to be sorted by release date! Why would the macro not make it possible to honor all details of the filter driving the issue list? Extremely frustrating. The macro should include a control to set the display order either to be pulled from the filter, or to be set independently in the pulled list, similar to the existing ability to sent columns to display in the macro indepently from the filter's view. 

            Kel Hill added a comment - This deficiency makes Confluence useless to me for publishing our release notes. I need my release notes to be sorted by release date! Why would the macro not make it possible to honor all details of the filter driving the issue list? Extremely frustrating. The macro should include a control to set the display order either to be pulled from the filter, or to be set independently in the pulled list, similar to the existing ability to sent columns to display in the macro indepently from the filter's view. 

            Shannon Graham added a comment -

            This should be a bug - we are creating/updating and sharing filters created for a reason.

            Shannon Graham added a comment - This should be a bug - we are creating/updating and sharing filters created for a reason.

            René Bonte added a comment -

            When pre-defined ordering in JQL is used, the ordering using the columns (arrows) on rendered page no longer works.

            Is fixing that part of this suggestion, or should we create a bug for that?

            René Bonte added a comment - When pre-defined ordering in JQL is used, the ordering using the columns (arrows) on rendered page no longer works. Is fixing that part of this suggestion, or should we create a bug for that?

            Anna Olenberg added a comment -

            also think that this should be a bug, not just suggestion. please fix this. 

            Anna Olenberg added a comment - also think that this should be a bug , not just suggestion. please fix this. 

            Daniel PHAN added a comment -

            Please fix this bug, so that the ORDER BY clause from Jira filter gets correctly taken into account in Confluence Jira Issues Macro.

            Thanks!

            Daniel PHAN added a comment - Please fix this bug, so that the ORDER BY clause from Jira filter gets correctly taken into account in Confluence Jira Issues Macro. Thanks!

            james_m_brown1210241387 added a comment -

            Just upgraded to Confluence Server 6.9.10 with 2K user license. This issue is extremely serious because we use the Jira Issue filter table for traceability requirement documents.

            james_m_brown1210241387 added a comment - Just upgraded to Confluence Server 6.9.10 with 2K user license. This issue is extremely serious because we use the Jira Issue filter table for traceability requirement documents.

            Jason Liwag added a comment -

            The same here for Confluence 6.0.6 (Server)

            . 

            Jason Liwag added a comment - The same here for Confluence 6.0.6 (Server) . 

            Carol Jones added a comment -

            Just confirmed this same issue on Server installation - CONF v5.10

            Also agree that it should be changed from a Suggestion issue type to a Bug issue type.

            Carol Jones added a comment - Just confirmed this same issue on Server installation - CONF v5.10 Also agree that it should be changed from a Suggestion issue type to a Bug issue type.

            Brian Clark added a comment -

            I was able to work around this issue by placing the entire JQL statement, with the ORDER BY statement on the end, into the macro within Confluence. This worked both when viewing the page and upon export to another format. Running Confluence 5.6.4.

            I still think this is a bug, however, because the Confluence documentation specifically states that this macro supports JIRA URLs. Sorting is part of filters which are JIRA URLs.
            https://confluence.atlassian.com/conf56/jira-issues-macro-658736879.html

            Display a table of JIRA issues onto your page, using a JIRA URL.

            Brian Clark added a comment - I was able to work around this issue by placing the entire JQL statement, with the ORDER BY statement on the end, into the macro within Confluence. This worked both when viewing the page and upon export to another format. Running Confluence 5.6.4. I still think this is a bug, however, because the Confluence documentation specifically states that this macro supports JIRA URLs. Sorting is part of filters which are JIRA URLs. https://confluence.atlassian.com/conf56/jira-issues-macro-658736879.html Display a table of JIRA issues onto your page, using a JIRA URL.

              Unassigned Unassigned
              8d062e30a5d2 Nick Spacek
              Votes:
              105 Vote for this issue
              Watchers:
              61 Start watching this issue

                Created:
                Updated: