Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bugzilla API 0.2 Released

4 views
Skip to first unread message

Gervase Markham

unread,
Nov 9, 2009, 5:50:21 PM11/9/09
to
Version 0.2 of the Bugzilla REST API has been released:
https://wiki.mozilla.org/Bugzilla:REST_API
https://wiki.mozilla.org/Bugzilla:REST_API#Version_0.2_.2811th_November_2009.29

New in this version:

* Read/write support for flags, groups, custom fields and comment
privacy
* Access to all aspects of Bugzilla's configuration with a new
/configuration call
* More comprehensive documentation
* Better logging so I can debug problems

Note that these new capabilities will not be available on the copy of
the API pointed at bugzilla.mozilla.org until the upgrade :-( But in the
mean time, you can test them on the staging server. Although that seems
very slow at the moment.

I consider this the first version of the API with which you should be
able to write a capable Bugzilla client of some sort. Let me know if you
find stuff missing which would be required for this usage.

There is now a Bugzilla component for you to file bugs in:
https://bugzilla.mozilla.org/enter_bug.cgi?product=Webtools&component=BzAPI
:-)

Gerv

Axel Hecht

unread,
Nov 17, 2009, 5:45:57 PM11/17/09
to

Hey, tools.

One configuration piece I'm currently scraping for my bug-filing tool is
who's on default on bugs in a particular component. I use this to CC the
usual suspects for a particular locale. I currently have some js that I
run to scrape that data, the comments at
http://hg.mozilla.org/users/axel_mozilla.com/dashboard/file/default/scrape_l10n_components.js
say it all, I guess. Yikes. What did I do?

2nd post.

Axel

Axel Hecht

unread,
Nov 17, 2009, 6:17:20 PM11/17/09
to

Clarification, goal of that exercise to be able to file a bug with the
'ar', 'he', 'tr' teams on CC.

Axel

Gervase Markham

unread,
Nov 18, 2009, 5:39:55 AM11/18/09
to
On 17/11/09 22:45, Axel Hecht wrote:
> One configuration piece I'm currently scraping for my bug-filing tool is
> who's on default on bugs in a particular component. I use this to CC the
> usual suspects for a particular locale.

If they are the "default CCs" or default assignee/QA contact, doesn't
Bugzilla put them in their right positions automatically when you file a
bug? Why do you need to know who they are?

Certainly, if you file a bug via the HTTP API or XML-RPC API, the
minimum you need to provide is a summary, product, component and
version. Bugzilla will fill in all the rest for you.

Gerv

Gervase Markham

unread,
Nov 18, 2009, 5:41:07 AM11/18/09
to
On 17/11/09 23:17, Axel Hecht wrote:
> Clarification, goal of that exercise to be able to file a bug with the
> 'ar', 'he', 'tr' teams on CC.

Which of the data on the page
https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Localizations
gives you the Bugzilla IDs of the "ar" team?

Gerv

Axel Hecht

unread,
Nov 18, 2009, 6:28:44 AM11/18/09
to

I just CC arab...@localization.bugs and the arabic team better be
watchin' that.

I use that generated page in three scenarios:

- filing a bug per locale. Easy, just gotta guess the right component.
- filing one bug per locale. Trickier, those usually end up in either
the "Others" component in Mozilla Localizations, or even in, say, Firefox.
- putting particular l10n teams on CC on platform or application bugs.
Then I just select the locale teams and copy the CC text.

I'm taking both default owner and QA contact, if not nobody. Being able
to get defaultCC would just be an RFE on top of that, not sure if that
had privacy concerns.

Axel

Gervase Markham

unread,
Nov 20, 2009, 6:55:58 AM11/20/09
to
On 18/11/09 11:28, Axel Hecht wrote:
> I just CC arab...@localization.bugs and the arabic team better be
> watchin' that.

Right. So why do you need to scrape Bugzilla for this data? Wouldn't it
make more sense to standardise the names of those default-QAs to e.g.
xx...@localization.bugs, then you would just be able to generate the
right email address without asking Bugzilla?

I mean, I could add information about who the default assignee, QA
contact and CCs are to the Configuration object, but it's already
massive, and I don't see much use for the data because normally people
just file bugs and those addresses get added automatically.

You seem to have the unusual use case of wanting to use the default
assignee/QA/contact/CC for component A in a bug filed in component B.

Gerv

Axel Hecht

unread,
Nov 20, 2009, 7:11:31 AM11/20/09
to

Well, yeah. Kinda maps to the "we have reached a local minimum in the
usefulness of our taxonomy" in the other thread.

I'm a little hesitant to just move the existing long standing bugzilla
settings over, and even the new ones aren't easy to guess. Not sure why
and when we started to have the language in there.

Longer discussion for a different group, and part of the other
discussion in .governance, at least in part. I wish we wouldn't ship
software, then I could actually think about that for a bit and play around.

Axel

Gervase Markham

unread,
Nov 23, 2009, 11:36:12 AM11/23/09
to
On 20/11/09 12:11, Axel Hecht wrote:
> I'm a little hesitant to just move the existing long standing bugzilla
> settings over, and even the new ones aren't easy to guess. Not sure why
> and when we started to have the language in there.

You mean people's searches might break if you change the "email address"
associated with these accounts? Of course, watching etc. wouldn't break
because that's tied to the user ID, not the email address.

> Longer discussion for a different group, and part of the other
> discussion in .governance, at least in part. I wish we wouldn't ship
> software, then I could actually think about that for a bit and play around.

:-)

Gerv

0 new messages