New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: JRA-10758
Type: Bug Bug
Status: Resolved Resolved
Resolution: Duplicate
Priority: Major Major
Assignee: Unassigned
Reporter: Daniel Hannum
Votes: 1
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

RSS and Permlink URLs are incorrect when using Toolkit multi-issue searcher

Created: 03/Aug/06 01:17 PM   Updated: 17/Aug/06 03:31 AM
Component/s: Custom Fields, Filtering & Indexing
Affects Version/s: 3.6.3
Fix Version/s: None

Time Tracking:
Not Specified

Environment:
standalone, jrocket
JIRA Toolkit 0.7.8 (for JIRA 3.6.x)
Issue Links:
Reference
 

Participants: Daniel Hannum and Jeff Turner [Atlassian]
Since last comment: 2 years, 1 week, 5 days ago
Resolution Date: 17/Aug/06 03:31 AM
Labels:


 Description  « Hide
As mentioned deep in the comments of JRA-7068, the RSS URL produced by queries that use the JIRA Toolkit Multi-issue searcher are incorrect. It appears as though all other conditions on the filter are represented in the resulting URL, but no multi-issue keys. Make a query that uses only Multi-issue keys, and the resulting RSS will be the entire database. This makes Multi-issue keys unusable with the Confluence {jiraissues} macro.

Additionally, the PermLink link is also wrong for the same reason. You'll get a filter of the entire DB if you click permlink on a filter that uses only Multi-issue keys.

The comment in JRA-7068 mentions adding "&customfield_10190=JRA-1000,JRA-2000" on the end of the URL (adjusting the custom field # for your installation). This works for both the permlink URL and the RSS URL.

I want to make sure this is tracked in its own right. There is a workaround, but I can't expect my not-always-technical PM's to hack up URLs.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Jeff Turner [Atlassian] added a comment - 17/Aug/06 03:31 AM
Please track this bug at its new home, http://developer.atlassian.com/jira/browse/JTOOL-2