Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.planning
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion bugzilla.mozilla.org improvements
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Daniel Veditz  
View profile  
 More options Jun 12 2009, 7:39 pm
Newsgroups: mozilla.dev.planning
From: Daniel Veditz <dved...@mozilla.com>
Date: Fri, 12 Jun 2009 16:39:05 -0700
Local: Fri, Jun 12 2009 7:39 pm
Subject: Re: bugzilla.mozilla.org improvements
Print | View thread | Show original | Report this message | Find messages by this author

Gervase Markham wrote:
> On 12/06/09 12:49, Axel Hecht wrote:
>> 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.

> Is it good enough to have the JSON API have the same capabilities as the
> current query page, or do you need more?

Note that current queries support both XML and CSV output, and the query
request can specify the columnlist you want for the output.

>> 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-.*'"

> One additional thing I'll guess you need is an option to return a count
> rather than the bug data?

you can get the count of a single query using ctype=microsummary, but if
you wanted the number "per component" you have to write one query per
component and run each of them separately.

What I think he wants (and if he doesn't I do) is support for GROUP BY.
If we had this feature and it just generated a "group count" column then
we could read the output using the currently supported output formats
(plus JSON if you add a general JSON option).

-Dan


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google