The Bugzilla 4.0 API doesn't seem to regard any methods as experimental or unstable anymore. CoreException: XMLRPC is not availableĪt .(BugzillaClient.java:2374)Īt .圜onnector.getTaskHistory(BugzillaRepositor圜onnector.java:1083)īugzilla contains important data for all Eclipse projects and I think these data should be accessible. My latest try was to use Mylyn's APIs, but also Mylyn cannot retrieve any bug stats without XMLRCP: I made a couple of approaches to get hold of some bug stats, including screen-scraping the history HTML files etc, but that's of course horrible. Bugzilla itself offers some stats, but there are not useful as they do not show progress over time. Since years, I try every now and then to get some usable bug stats for our project, but no avail. If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.I would also like to ask you to re-consider this decision. Use thereof is explained in our trademark policy (see Project:Copyrights for details). Their respective logos and icons are also subject to international copyright laws. "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries.
#BUGZILLA XML RPC CODE#
This does not include the source code of LibreOffice, which is licensed under the GNU Lesser General Public License ( LGPLv3). Please note that all contributions to The Document Foundation Wiki are considered to be released under the Creative Commons Attribution-ShareAlike 3.0 Unported License, unless otherwise specified.All other fields are standard XML-RPC types. As of Bugzilla 3.6, Bugzilla always expects dateTime fields to be in the UTC timezone, and all returned dateTime values are in the UTC timezone. They should be in YYYY-MM-DDTHH:MM:SS format (where T is a literal T). Based on work by Dennis Roczek and Dennis Roczek and others. dateTime fields are the standard dateTime.iso8601 XML-RPC field.
This page was last edited 09:50:36, by Ilmari Lauhakangas.If there's a tool or a workflow that you'd like to consider implementing that needs additional help on the backend, please talk with us, and we'll do our best to help you out. Here's a field list grabbed elsewhere, so YMMV:Īfter migration to our own Bugzilla instance, we will have more flexibility in what methods of data export we make available. &columnlist=bug_id,product,component,assigned_to,bug_status,short_desc,op_sys,status_whiteboard,keywords &query_format=advanced&limit=0&ctype=csv&human=1 Here's an example including Bug ID, Product, Component, Assignee, Status, Summary, Operating System, Whiteboard, and Keywords:Ĭolumnlist=bug_id,product,component,assigned_to,bug_status,short_desc,op_sys,status_whiteboard,keywords To export a different set of columns, you'll need to specify them in your URL, formatted using the internal variable names. The set of columns that will be exported is set in your local config/cookie (AFAIK). &product=LibreOffice&query_format=advanced&limit=0& ctype=csv&human=1 note that we've lost the order term, and gained values for ctype and human. Here are the changes necessary to get a CSV text file instead of an HTML page: note the difference, highlighted in bold. &product=LibreOffice&query_format=advanced &limit=0&order=priority%2Cbug_severity. If we want to remove the limit, here's the change:
&product=LibreOffice&query_format=advanced Here's the standard URL to search for all UNCONFIRMED bugs in the browser (limited to 500): Here's an example of a simple search URL with the following parameters: (Note: this information may change - please check with TDF sysadmins for further information) CSV ExportĮxporting data in CSV format is relatively straightforward if you know some tricks :-) If you're connecting to it with a tool like the Mediawiki-Bugzilla plugin, this information will prove useful:
We use the XML-RPC interface for the Bugzilla-MediaWiki plugin: There are multiple APIs for export (and other data manipulation).
0 kommentar(er)
