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

      In the new release of the JIRA issues macro, it is not possible to short the columns inside a table.

      This feature request is to sort columns from viewpage for the JIRA issues macro.

            [CONFSERVER-30114] Ability to sort issues in the JIRA issues macro table

            I've just encountered the issue of the Jira Issues table in Confluence not obeying the column sort order reliably when clicking the sort arrows too.

            I was able to pre-sort the table by the column I wanted by adding the required "order by XYZ desc / asc" to the JQL, but then I found that when I tried to sort the columns of the resulting table by clicking the up/down arrows in the table headers, the JQL query broke and Jira sent back an error.

            Urrggh, it seems clicking the sort arrows tacks on the "order by XYZ desc / asc" so if that's already in the JQL, the double-up isn't accepted by Jira.

            David Bakkers added a comment - I've just encountered the issue of the Jira Issues table in Confluence not obeying the column sort order reliably when clicking the sort arrows too. I was able to pre-sort the table by the column I wanted by adding the required "order by XYZ desc / asc" to the JQL, but then I found that when I tried to sort the columns of the resulting table by clicking the up/down arrows in the table headers, the JQL query broke and Jira sent back an error. Urrggh, it seems clicking the sort arrows tacks on the "order by XYZ desc / asc" so if that's already in the JQL, the double-up isn't accepted by Jira.

            I'm trying to sort by Rank (pretty common).  However the only way I can get this to sort is to display a rank value that does not make sense for humans.  Then click on the rank column?  This is sad.  Can this not get fixed?

            Damon Gaylor added a comment - I'm trying to sort by Rank (pretty common).  However the only way I can get this to sort is to display a rank value that does not make sense for humans.  Then click on the rank column?  This is sad.  Can this not get fixed?

            We still see this but browser to browser behavior is different. Chrome allows sorting, Safari does not.

             

            Matthew Thompson added a comment - We still see this but browser to browser behavior is different. Chrome allows sorting, Safari does not.  

            G added a comment -

            We are using Confluence 5.7.1 and JIRA 7.2.4. When we use the JIRA Issues Macro on Confluence page we are not able to sort it. Even if we do the sort on JIRA filter, the sort itself is not reflected on Confluence.

            One way we can get the correct sort to display on confluence is by adding the JIRA issues macro with the JQL query having the sort rather than referencing the filter.

             

            Cheers,

            Gaj

            G added a comment - We are using Confluence 5.7.1 and JIRA 7.2.4. When we use the JIRA Issues Macro on Confluence page we are not able to sort it. Even if we do the sort on JIRA filter, the sort itself is not reflected on Confluence. One way we can get the correct sort to display on confluence is by adding the JIRA issues macro with the JQL query having the sort rather than referencing the filter.   Cheers, Gaj

            James Liu added a comment - - edited

            This is related to the export of the sorted view reverting back to it's default sorting value (last updated first), rather than retaining the viewed sort value when exporting the page to pdf.

            James Liu added a comment - - edited This is related to the export of the sorted view reverting back to it's default sorting value (last updated first), rather than retaining the viewed sort value when exporting the page to pdf.

            Mainly as an attempt to clarify: In Confluence < 5.5 the JIRA issue macro table showed table rows which were non-sortable. From the comment and the description here I take it that this was changed to resolve the issue in Confluence 5.5 by making the rows sortable/clickable in the viewer.

            If I'm right, the comments relating to keeping the sort order of a JIRA issue navigator link is a separate issue independent from this one and the problem pointed out by others that some columns are non-sortable/-clickable in Confluence 5.7 point to a new/different issue.

            Stefan Hett added a comment - Mainly as an attempt to clarify: In Confluence < 5.5 the JIRA issue macro table showed table rows which were non-sortable. From the comment and the description here I take it that this was changed to resolve the issue in Confluence 5.5 by making the rows sortable/clickable in the viewer. If I'm right, the comments relating to keeping the sort order of a JIRA issue navigator link is a separate issue independent from this one and the problem pointed out by others that some columns are non-sortable/-clickable in Confluence 5.7 point to a new/different issue.

            Nick added a comment -

            Sorry Jonas - hadn't noticed - I've voted for your cloned one

            Nick added a comment - Sorry Jonas - hadn't noticed - I've voted for your cloned one

            With this ticket being closed i have no chance of voting on it =(

            Jonas Andersson added a comment - With this ticket being closed i have no chance of voting on it =(

            Nick added a comment - - edited

            From what I've seen, there is no solution in place. Just call it lazy coding from Atlassian. Vote for it and they might take a look and admit to the bug.

            Nick added a comment - - edited From what I've seen, there is no solution in place. Just call it lazy coding from Atlassian. Vote for it and they might take a look and admit to the bug.

            I am also seeing this issue in Jira 6.2.1 vs confluence 5.5 after updating the jira macro on confluence. What was the solution to get it to work anyway? Don't see it in the ticket.

            Jonas Andersson added a comment - I am also seeing this issue in Jira 6.2.1 vs confluence 5.5 after updating the jira macro on confluence. What was the solution to get it to work anyway? Don't see it in the ticket.

              ndang Nguyen Dang
              smansour Sherif Mansour
              Votes:
              18 Vote for this issue
              Watchers:
              36 Start watching this issue

                Created:
                Updated:
                Resolved: