My pet would be a truly-JSON API to get data out of bugzilla. Our use
case is the l10n dashboard, which we'd like to have bugilla integrated
with. I'll probably need to get to my drawing board to give some
concrete queries we'd want. Here having aggregated data is a big win,
too. 75 queries to bugzilla suck, where we'd really want something like
"number of open bugs per component in l10n" or "number of open blockers
of bugs with an alias matching 'fx35-l10n-.*'"

A smaller thing would be to support filling in the alias via the URL. I
have forms that generate those urls from data, so having the alias makes
sense (more than in the case of static links). This is bug 310532. When
filing the flock of bugs for new locales, getting the alias right is
manual work each time.

I guess that finding out a better way to have "fixed here, but needs
fixing somewhere else" would be cool, and support for that in queries.

Shorter query urls by default, maybe.

Better caching? Not sure, but I think we reload a lot these days.

I guess that's my ad-hoc list.

Axel