It seems that inserting a group of Jira issues in a Confluence page using the Jira Issues macro isn't honoring the underlying filter's sort order. I've attempted to address this through the use of Bob Swift's great Table-Plus macro (why aren't those capabilities baked into Confluence??!!) ... but my attempts to specify a default sort column in that way have also failed.
Anybody run into this before? Any help is greatly appreciated.
I believe what I've run into is simply a problem with the versino of the Jira Macro plugin we're currently using. Until we update to the latest version of Confluence, however, we're not able to update the macro plugin. I'll call this answered for now and am hopeful that once we complete the necessary upgrades, the problem will be resolved.
I'd like to log a new Improvement request. The latest version of Confluence allows to you sort the table after the fact, but still does not respect the filter's ordering when defined. Seems to me like when I'm creating a document I am doing so to define the way I want data displayed to recipients, and if they have to interact with the document in order to see the information in the way I wanted to display it, something is missing.
Created an improvement request here: https://jira.atlassian.com/browse/CONF-35323
It has been nearly three years and this issue appears to still be broken. The suggestion in the above comments is that we go to a closed ticket in whose comments a plugin vendor offers a solution we have to pay for.
Controlling the default sort of any table or report is one of the most basic functions possible. Why is this still not fixed?
I also have a filter in Jira written in JQL that contains custom field criteria, and ORDER BY statement, and also custom filter columns.
When the filter gets embedded in my confluence page, I lose the custom filter columns and the ORDER BY property.
I can work around the custom filter columns by manually selecting the columns to display (interestingly, the column names are displayed in their multilingual translation that I translated), but there doesn't seem to be a way to set the default sorting. Currently I have to teach my users to manually click on the sorting twice to get the proper descending sort.
Would be great if the embedded filter would simply honour the original JIRA sort properties and custom columns.
Same issue, same complaint.
We've created filters with sort orders that are used through out our organization, so that when we change or adjust a filter everyone gets the benefit without needing to edit / change a bunch of separate JQL.
When using those filters, we need to just say "filter=foobar".
We then need any use of those filters to honor the entire filter instead of only a portion of it, otherwise it significantly devalues the benefit of using filters.
Hi my Community friends! For those who don't know me, I'm a product marketer on the Confluence Cloud team - nice to meet you! For those of you who do, you know that I've been all up in your Co...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs