Bug 62935 - BUGZILLA: Modify Atom-Feeds for Bugzilla (need to be limited)
Summary: BUGZILLA: Modify Atom-Feeds for Bugzilla (need to be limited)
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: WWW (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-30 11:57 UTC by retired
Modified: 2013-05-30 12:36 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description retired 2013-03-30 11:57:10 UTC
Problem description: 
The current Atom-Feeds won't work in any RSS-client because the amount of items is just too big. The feed needs to be limited. Thus I'm requesting to modify the default feed URLs (suggestions below),

1 All open bugs
Steps to reproduce:
Browser URL: https://bugs.freedesktop.org/buglist.cgi?bug_status=__open__&list_id=270795&product=LibreOffice&query_format=specific&order=changeddate%20DESC%2Cbug_status%2Cpriority%2Cassigned_to%2Cbug_id&limit=0
current Atom-Feed: https://bugs.freedesktop.org/buglist.cgi?bug_status=__open__&list_id=270795&product=LibreOffice&query_format=specific&order=changeddate%20DESC%2Cbug_status%2Cpriority%2Cassigned_to%2Cbug_id&limit=0buglist.cgi?bug_status=__open__&limit=0&list_id=270795&product=LibreOffice&query_format=specific&title=Bug%20List&ctype=atom

Current behavior: RSS-Reader doesn't catch a single item.

Expected behavior: Feed gets updated correctly.

The following URL should be the new default: https://bugs.freedesktop.org/buglist.cgi?bug_status=__open__&list_id=264812&product=LibreOffice&query_format=specific&order=changeddate%20DESC%2Cbug_status%2Cpriority%2Cassigned_to%2Cbug_id&query_based_on=buglist.cgi?bug_status=__open__&list_id=264812&product=LibreOffice&query_format=specific&title=Bug%20List&ctype=atom&limit=50
(note the limit at the end of the URL).

2 All closed bugs
Steps to reproduce:
Browser URL: https://bugs.freedesktop.org/buglist.cgi?bug_status=__closed__&product=LibreOffice&query_format=specific&order=changeddate%20DESC%2Cbug_status%2Cpriority%2Cassigned_to%2Cbug_id&list_id=270802

Current behavior: RSS-Reader doesn't catch a single item.

Expected behavior: Feed gets updated correctly.

The following URL should be the new default: https://bugs.freedesktop.org/buglist.cgi?bug_status=__closed__&content=&product=LibreOffice&order=changeddate%20DESC%2Cbug_status%2Cpriority%2Cassigned_to%2Cbug_id&ctype=atom&limit=50
(note the limit at the end of the URL).
              
Operating System: All
Version: unspecified
Comment 1 Rainer Bielefeld Retired 2013-03-30 12:45:20 UTC
Hm, I only use feeds to get information concerning latest changes, for example "New reports yesterday" of so. Here the query already does the limitation, that works for me without any problem. I think most other users have the same needs, and I doubt that many users use such "all bugs Feeds" like your example. So I doubt that the awaited benefit justifies any effort. But let' s se

@438753924:
Please start a discussion on <libreoffice-qa@lists.freedesktop.org> to check whether that is a "real life" problem.
Comment 2 Zeki Bildirici 2013-05-18 20:34:09 UTC
Hi,

I would like to point one important issue about the feeds generated FDO's bugzilla FEED link,

Currently you may see this feeds correct order(ascending-descending etc) but RSS readers like Akregator or external web tools, the feed is misses the order syntax. You should add the following tag manually:

&order=bug_id%20DESC&

See #fdo50096 https://bugs.freedesktop.org/show_bug.cgi?id=50096 

Regards,
Zeki
Comment 3 retired 2013-05-30 12:36:41 UTC
I'm closing this. Maybe to specific and we should rather try to provide good links for bug triagers in the wiki with additional info. Maybe there we could offer some RSS feeds to keep up with changes. Let's just do that, once we find some time to clean the wiki further. QA wiki cleaning is already ongoing so we'll deal with this eventually but not really worth a bug ticket.