Modify ↓
      
#2253 closed defect (fixed)
RSS for Custom Query should include the constraints as a query string in the channel link
| Reported by: | Owned by: | Matthew Good | |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.9.4 | 
| Component: | ticket system | Version: | 0.9b1 | 
| Severity: | minor | Keywords: | rss | 
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
When I make a Custom Query and bookmark the RSS feed, that URI  contains a querystring. For example: http://projects.amor.org/amor/query?status=new&group=&format=rss&order=priority. The bit after the "?" is what I mean by "querystring".
The resultant XML starts with:
<?xml version="1.0"?> <rss version="2.0"> <channel> <title>Amor Ministries: Ticket Query</title> <link>http://projects.amor.org/amor/query</link>
…but the href in the link element isn't very helpful, since it takes me back to the custom query page without any of the parameters I already specified. If the query_rss.cs included the constraints as a querystring, that would be much more helpful.
Attachments (0)
Change History (4)
comment:1 by , 20 years ago
comment:2 by , 20 years ago
| Milestone: | → 0.9.4 | 
|---|
comment:3 by , 20 years ago
| Owner: | changed from to | 
|---|---|
| Status: | new → assigned | 
comment:4 by , 20 years ago
| Resolution: | → fixed | 
|---|---|
| Status: | assigned → closed | 
  Note:
 See   TracTickets
 for help on using tickets.
    


  
I'm using mod_python, by the way, so I just made a quick hack:
…and then referenced query.qs in the template. But a more robust solution would probably have to re-deconstruct the constraints dict in trac.ticket.query.QueryModule.process_request.