Data on Drupal.org is now available as JSON through an API:
This would circumvent some of the fragility of parsing the full XHTML pages of the issue queue, and it includes paging information, so it's possible to go back to two requests per count (first page + last page), instead of iterating through every page to find the end.
By default the responses include a lot of information on each issue (e.g. full issue description, attached files, comment ids...) but this can be limited by providing full=0 as a parameter.
It looks like the parameters use internal field names and IDs rather than the nice names that the front end uses, so the configuration will need to be updated or mapped (e.g. priorities => field_issue_priority).
The info page also doesn't indicate how to specify multiple parameters (e.g. a set of statuses).
e.g. https://www.drupal.org/api-d7/node.json?type=project_issue&field_project=3060&field_issue_status=8&field_issue_version=8.0.x-dev&field_issue_priority=200&full=0
Data on Drupal.org is now available as JSON through an API:
This would circumvent some of the fragility of parsing the full XHTML pages of the issue queue, and it includes paging information, so it's possible to go back to two requests per count (first page + last page), instead of iterating through every page to find the end.
By default the responses include a lot of information on each issue (e.g. full issue description, attached files, comment ids...) but this can be limited by providing
full=0as a parameter.It looks like the parameters use internal field names and IDs rather than the nice names that the front end uses, so the configuration will need to be updated or mapped (e.g.
priorities=>field_issue_priority).The info page also doesn't indicate how to specify multiple parameters (e.g. a set of statuses).
e.g. https://www.drupal.org/api-d7/node.json?type=project_issue&field_project=3060&field_issue_status=8&field_issue_version=8.0.x-dev&field_issue_priority=200&full=0