-
Suggestion
-
Resolution: Fixed
In the new JIRA Issues Macro for confluence, we're trying to allow users to sort and page on the fly, via ajax. We're doing that by changing and appending things in the URL, like a new sort order, or a new pager/start variable. This works well for normal JIRA Issue Filter URLs, like this one:
However, if you try to get a URL from a saved filter, you get a URL like this:
New sort orders on this URL are simply ignored, and the results returned in the original order. For example:
Parameters on the URL should override the default settings of a saved filter.
[JRASERVER-15313] Saved Filter URLs do not respect additional parameters
I'm not sure how much of the filter we should override. I feel like it's reasonable to override the sorting and the paging, but overriding other things seems like a bad idea as it actually changes what the filter searches and not just how it returns it.
Cheryl Jerozal [Atlassian]
added a comment - chris, you should be able to get just the key and due columns with the current version of the jiraissues macro. if you are still experiencing this problem, please file an issue here with any details you have:
http://developer.atlassian.com/jira/browse/CONFJIRA
also, fyi – unfortunately, we have had to push back the release of the new version of the jiraissues macro. now the new version that will allow any columns to be specified will not be included with confluence until the major release after 2.9
Cheryl Jerozal [Atlassian]
added a comment - chris, you should be able to get just the key and due columns with the current version of the jiraissues macro. if you are still experiencing this problem, please file an issue here with any details you have:
http://developer.atlassian.com/jira/browse/CONFJIRA
also, fyi – unfortunately, we have had to push back the release of the new version of the jiraissues macro. now the new version that will allow any columns to be specified will not be included with confluence until the major release after 2.9
Hi Chris, apologies – that doc is a little ahead of its time. You should be able to specify the columns you want in the next version of Confluence: 2.9.
Chris Wilkes
added a comment - This page says that I should be able to pass in "columns=key;due" and get back only those columns:
http://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro
However all the columns ( Key Summary Assignee Reporter Pr Status Res Created Updated Due) come back.
Also are those the only columns that can be specified? Ideally I would like to have time spent and estimate time remaining – then I can just look at a confluence page and see what work's been done.
Chris Wilkes
added a comment - This page says that I should be able to pass in "columns=key;due" and get back only those columns:
http://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro
However all the columns ( Key Summary Assignee Reporter Pr Status Res Created Updated Due) come back.
Also are those the only columns that can be specified? Ideally I would like to have time spent and estimate time remaining – then I can just look at a confluence page and see what work's been done. JIRA never had this functionality, even when getting the HTML view of a saved filter. It was never designed to provide this functioanlity.
Therefore I have changed this to improvement from bug.
Marking as resolved because the paging and sorting are all that are needed for the JIRA issues macro and I'm convinced at this point that allowing anything else to be overridden changes the meaning of the filter too much. If there are other cases, or someone else feels otherwise, we can reopen this and discuss.