Json interface for issue queue. [#2225495]

Updated: Comment #N

Problem/Motivation

We need a JSON interface for polling the issue queue.
So we know which issues where updated in the last X minutes, as an example.

Proposed resolution

Have https://drupal.org/project/issues/json available with X last updated issues. With an extra contextual filter to limit a timeframe. "Return last updated issues within 60 minutes".

Remaining tasks

Test https://drupal.org/project/views_datasource
Get a GO from the D.O overlords?

Comments

Comment #1

drumm

he/him

NY, US

CreditAttribution: drumm commented 25 March 2014 at 21:45

Status:

Active

» Postponed (maintainer needs more info)

Every issue page has an RSS feed available, which also filters down the issue queue, in case you don't want all of the issues. RSS may be an old-school format, but it is machine readable. What other advantages does this have?

Comment #2

betz CreditAttribution: betz commented 25 March 2014 at 21:49

There are 2 things, first, an exposed filter for limiting on updated date.
Secondly, have consistency with the issues that will be available as json.

If this is not interesting, maybe just add the updated date to the RSS feed.
And if possible, add the exposed filter.

Comment #3

drumm

he/him

NY, US

CreditAttribution: drumm commented 25 March 2014 at 22:03

Adding to the RSS feed displays would be good. Then we do not have more Views or Displays to maintain. These are exported to the drupalorg_searchapi_issue_views Feature, where there are already ~5 Views with RSS.

Comment #4

pflame CreditAttribution: pflame commented 31 July 2014 at 18:50

Status:

Postponed (maintainer needs more info)

» Active

I and my company working on visualizing the Drupal 8 issues. The visualizations that we built are Number of Issues by component and status (http://azrisolutions.com/d8issuesviz) and Critital to Minor issues by Component & Status (http://azrisolutions.com/d8issuesvizbypriority)

Today at CapitalCampDC we talk with Cathy(YesCT) and David (davidhernandez) about how we can improve the visualization and make it more useful for the community. We have got very good suggestions.

To proceed further we need the drupal issues information available for public. Currently I am scraping the information from drupal.org. Cathy and David suggested me to re-open this ticket.

Currently I need information of issue meta data and comments information for the further work.