question on the state of Bugzilla WebService API
dwilliss at microimages.com
Tue Oct 30 14:29:07 UTC 2007
I would really like to see a Webservice API way to change a bug's
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
I would rather do it through the Webservice API so taht bugzilla could
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.
Mads Bondo Dydensborg wrote:
> 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
>>> too stupid to embed the mylyn-api in my program correctly, I have to rely
>>> 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 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.
>> To view or change your list settings, click here:
More information about the developers