This message was deleted.

You can access the tags on the '*-attributes' endpoints. It's not exactly what you want because you can't filter right away on the 'builds' endpoint. But we didn't want to add tons of query parameters, and preferred being not opinionated.

yep, I'm doing that...just that it's wasting time and server resources downloading those extra build responses... 🙂

Agreed. It's just that there are many interesting things to filter on, not just tags. What you want to do makes sense and is very 'classic' so let's see

there are definitely a lot of things to filter on....but I suppose you have analytics that show how people use filtering in the UI? I suspect tags is one of the highest, followed by the gradle command (at least that's how I use the UI as well) 🙂

We don't have analytics on private Gradle Enterprise instances. As said your cases are very valid. We'll discuss and see which direction we want to go with this.