The project issue module currently provides an RSS feed that provides the issue title and teaser. I propose that you include additional XML fields for priority, status, category, and component. Some RSS readers may show these, many will ignore them, and a custom feed reader can use them.

I'm working on a ticket aggregator (using leech) that aggregates all my tasks across projects, d.o being just one. The goal is to be able to get to a single page that shows the issue status of all my tickets, whether it be for d.o or for one of my clients. For this to be useful, I really need priority and status.

I hope that this patch is rather un-invasive while allowing others to create powerful new features. I don't know if it will increase or decrease the load on d.o. I suspect that more people will aggregate their tickets if a ticket aggregator was easy to implement. But the question remains will that result in more or less page requests on d.o. Despite the performance question, it's a big productivity boost for me.

CommentFileSizeAuthor
#2 153640.patch1.42 KBdouggreen
rss_2.patch1008 bytesdouggreen
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

walkah’s picture

walkah CreditAttribution: walkah commented
Status: Needs review » Needs work

The problem here, but just adding random elements to the XML document renders the XML invalid (check with feedvalidator.org) ... this is apt to cause unexpected behavior in various parsers. /most/ readers will probably just silently ignore these *but*. Here's my $0.02:

I'd rather see this information included inside the <description> - so that it's actually visible and useful for people.

If you also want to include additional information, we should probably define a namespace for such custom extensions ...

douggreen’s picture

douggreen CreditAttribution: douggreen commented
Status: Needs work » Needs review
FileSize
153640.patch1.42 KB

I thought it was a cleaner XML implementation to put this stuff in tags, but if it will break RSS readers, then I'm fine with putting it in the <description>. See the attached patch, which is just slightly longer because of feed_item_length.

hunmonk’s picture

hunmonk CreditAttribution: hunmonk commented
Status: Needs review » Needs work

patch doesn't seem to apply anymore.

also, i think i'd like to see a more specific name for the theming function -- maybe theme_project_issue_rss_metadata()?