question on the state of Bugzilla WebService API

[Clement Chan]

Would someone comment on the current state of the Bugzilla WebService
API?

http://www.bugzilla.org/docs/3.0/html/api/

Normally, the project state can be STABLE, EXPERIMENTAL, or UNSTABLE.

We are planning to having some open source app integration with Bugzilla
3.0 via the Web Service API.

TIA,
- Clement

-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps...@lists.mozilla.org>

[Mads Bondo Dydensborg]

mandag 29 Oktober 2007 skrev Clement Chan:
> Would someone comment on the current state of the Bugzilla WebService
> API?

It works, but it can't really do that much (can create a bug, list some kind
of information and so on, but lots of functionality still lack). We (you and
I :-) need to write some more patches to introduce more functionality.

Some of the issues are listed here:

http://tinyurl.com/3afonu

Regards

Mads

--
Med venlig hilsen/Regards

Systemudvikler/Systemsdeveloper cand.scient.dat, Ph.d., Mads Bondo Dydensborg
Dansk BiblioteksCenter A/S, Tempovej 7-11, 2750 Ballerup, Tlf. +45 44 86 77 34

[Andreas Mayr]

Really good idea guys! I need this functionality too! As it seems, that I'm
too stupid to embed the mylyn-api in my program correctly, I have to rely on
the Bugzilla WebService API. And this functionality is really pretty poor :(

There are a few thing, that I'm missing in this buglist:
- get custom fields
- similar to products there should be a get_accessible_bugs method. It's
pretty long winded and slow at the moment to write a method, that retrieves
all bugs in the database

What do you think about that?

Best Regards,
Andi

-----Ursprüngliche Nachricht-----
Von: develope...@bugzilla.org [mailto:develope...@bugzilla.org] Im
Auftrag von Mads Bondo Dydensborg
Gesendet: Dienstag, 30. Oktober 2007 08:35
An: devel...@bugzilla.org
Betreff: Re: question on the state of Bugzilla WebService API

http://tinyurl.com/3afonu

Regards

Mads

--
Med venlig hilsen/Regards

<http://bugzilla.org/cgi-bin/mj_wwwusr?user=andrea...@kabelkom.at>

[Mads Bondo Dydensborg]

tirsdag 30 Oktober 2007 skrev Frédéric Buclin:
> Andreas Mayr a écrit :

> > Really good idea guys! I need this functionality too! As it seems, that
I'm
> > too stupid to embed the mylyn-api in my program correctly, I have to rely
on
> > the Bugzilla WebService API. And this functionality is really pretty
poor :(
>
>

> Several new methods will/should land on time for Bugzilla 3.2. mkanat is

Here is, from the top of my head, a list of stuff I would like to see. I think
most of it is not present:

(Create bug - is possible)

- Comment on a bug
- Change the status of a bug (inclusive closing it).
- List all open bugs, given a product
- List all open bugs, given a product and a component
- List all products (is implemented)
- List all components for a given product

I think adding these metods, where four are readonly, would hugely improve the
APIs usability.

Unfortunately, the focus of my company has shifted away from these tasks
currently.

Regards,

Mads

> currently working on fully implementing Bug->update which will let you
> edit all attributes of existing bugs, which is a huge improvement. I
> also hope we will be able to query the DB given some criteria (e.g.
> using the QuickSearch syntax, despite I know mkanat is not a fan of it)
> and get back a list of bug objects, which would also be a significant
> improvement. About administrative tasks, some work has been done in the
> backend which would let us implement some admin methods too.
>
> Even if we freeze in a few weeks to prepare Bugzilla 3.2 RC1, I see no
> reason to stop the implementation of new webservice methods as they
> don't affect the core code itself. We could discuss this topic at our
> Bugzilla meeting next week.
>
> LpSolit

> -
> To view or change your list settings, click here:

> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=m...@dbc.dk>
>
>
>

--
Med venlig hilsen/Regards

Systemudvikler/Systemsdeveloper cand.scient.dat, Ph.d., Mads Bondo Dydensborg
Dansk BiblioteksCenter A/S, Tempovej 7-11, 2750 Ballerup, Tlf. +45 44 86 77 34
-
To view or change your list settings, click here:

<http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps...@lists.mozilla.org>

[Andreas Mayr]

I agree with your suggestions. I was only listing a few things I've thought
of. Eg "list all components for a given product" would be very important.
For my work, I only need read-only features. Despite of this, I personally
think that it is in general better, to implement first all read-features
before concentrating on the modification-features.

-----Ursprüngliche Nachricht-----
Von: develope...@bugzilla.org [mailto:develope...@bugzilla.org] Im
Auftrag von Mads Bondo Dydensborg

Gesendet: Dienstag, 30. Oktober 2007 13:34

An: devel...@bugzilla.org
Betreff: Re: question on the state of Bugzilla WebService API

tirsdag 30 Oktober 2007 skrev Frédéric Buclin:

Regards,

Mads

--
Med venlig hilsen/Regards

<http://bugzilla.org/cgi-bin/mj_wwwusr?user=andrea...@kabelkom.at>

[Dave Williss]

I would really like to see a Webservice API way to change a bug's
status. This
should be able to add a comment at the same time.

We wrote an automatic distributed testing server. When a test fails, it
sends out emails
and somebody has to log a bugzilla item for it and log that number for
the test on the test
server. I could probably do this one through the webservice API, but we
want to keep a
human in the loop there. Later, when the test server determines that
the bugzilla item is
resolved as FIXED and that test is passing again, it changes its state
to VERIFIED and
adds a comment saying that it's now passing the auto test

Currently, it does this by cheating and writing records directly to the
bugzilla database.
I would rather do it through the Webservice API so taht bugzilla could
automatically
send out the email alerting people that it's changed. Currently we do
that via a cron
job which runs the script that checks and sends unsent notification emails.

Dave Williss
MicroImages, Inc.

[Frédéric Buclin]

Andreas Mayr a écrit :
> Really good idea guys! I need this functionality too! As it seems, that I'm
> too stupid to embed the mylyn-api in my program correctly, I have to rely on
> the Bugzilla WebService API. And this functionality is really pretty poor :(

Several new methods will/should land on time for Bugzilla 3.2. mkanat is

currently working on fully implementing Bug->update which will let you
edit all attributes of existing bugs, which is a huge improvement. I
also hope we will be able to query the DB given some criteria (e.g.
using the QuickSearch syntax, despite I know mkanat is not a fan of it)
and get back a list of bug objects, which would also be a significant
improvement. About administrative tasks, some work has been done in the
backend which would let us implement some admin methods too.

Even if we freeze in a few weeks to prepare Bugzilla 3.2 RC1, I see no
reason to stop the implementation of new webservice methods as they
don't affect the core code itself. We could discuss this topic at our
Bugzilla meeting next week.

LpSolit
-
To view or change your list settings, click here:

<http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps...@lists.mozilla.org>