Feedback on the Drupal.org API

I'm not exactly sure why, but https://www.drupal.org/api mentions that if you have API change requests, you should post them here. :) So, here goes!

I spend a good chunk of my Drupal life looking at issues in Google Spreadsheets in order to do issue triage, figure out what to fund through D8 Accelerate, etc. Google Spreadsheets has an API. Therefore, I thought a perfect use case for the Drupal.org API would be to populate a Google Spreadsheet with it. Here's what I found as I was doing so.

Problem #1: No way to do "AND/OR" queries within a given filter, esp. for status/version.

The most common thing I want to do is replicate the "- Open issues -" filter on any given issue view like https://www.drupal.org/project/issues/user. (Ideally, excluding "fixed," but I could always filter that in the spreadsheet.)

You can do a query like this to get critical, needs review issues against Drupal core 8.0.x, which is great:
https://www.drupal.org/api-d7/node.json?type=project_issue&field_project...

However, you can't do a query for "active|needs review|needs work|RTBC|postponed," so you must instead do one query for each status you care about. (In this case, at least 5 separate queries; more if there's a pager on any of them.)

So that's not ideal, but I can get by with 5 queries as long as I only want to query multiple values on a single filter. However, I'm always also going to want to replicate the issue view's "- 8.x issues -" filter, and so this becomes an exponential problem. There are currently 19 8.0.x-something statuses. 5*19 = 95 queries

(Since the criticals are pretty tightly triaged, I'm hard-coding version to 8.0.x-dev for now to avoid this problem, but there's definitely a chance I miss issues this way.)

One possible solution is to fix this in RestWS (relevant issue at #2308939: Make AND queries possible)

Another is to somehow expose those "- Open issues -" and "- 8.x issues -" filters at some weird ID like 999 or something so they won't conflict with anything else.

Problem #2: No way to determine a term's name without doing an extra query per term.

It's super-useful to be able to further filter this list by things like "has the Performance tag, but not the Triaged D8 Critical tag" or whatever. In theory, this is pretty easy since an issue node returned a query like the above has an array of its issue tags located in its taxonomy_vocabulary_9 property, so I could just concat them into comma-separated values and do a plain text search in the spreadsheet.

The problem is, the array only includes the term ID, not the term name, and I am just not nerdy enough to have all 10,000+ issue tag term IDs memorized (it is one of my many flaws). So I then need to query Drupal.org again for each term attached to an issue. Let's call the average number of tags attached to an issue (especially a critical Drupal core issue) 5. There are about 90 critical issues. That's an additional 450 requests to build this list. :(

(For now I am querying the database directly to populate a "look-up sheet" of common tag IDs/names to check first, hopefully cutting that number down significantly, but "normal" people will not have this option.)

I couldn't find a correlating RestWS issue, but adding the term name as a property in the taxonomy_vocabulary_9 array would be hugely helpful.

There are probably others, but as far as I got so far.